[Uptime] Support HTTP Common options for synthetics integration

[andrewvc]

With elastic/beats#27699 we now support a variety of new options for TLS and proxies when using zip_url sources for synthetics. These options only affect the download of the zip, not the operation of the browser. We should add these options to the synthetics integration UI.

The needed fields are documented fully in the beats PR. The short summary is as follows)

1. All TLS fields (same fields as in the HTTP UI for handling TLS). We should share a component here.
2. The proxy_url field

I think we can steal from the following portions of the HTTP integration UI with some modifications. I've included screenshots of that UI at the bottom of this ticket.

We will need to determine how this fits into the form, and crucially, how to communicate that these options affect the download of the zip, not the operation of the browser. I propose we add an expandable "Advanced Zip URL Settings" section with these settings put them one after the other, but am open to other ideas.

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[andrewvc]

@liciavale @drewpost do we need any explicit design here?

[drewpost]

I'm happy with re-using the patterns established elsewhere in the integration for this.

[liciavale]

Hey @andrewvc thanks for this. What does it happen when a user unselects the Enable TLS configuration? Do the settings below belong to this checkbox?

[dominiqueclarke]

@liciavale To answer your questions, the settings below indeed belong to the checkbox and only appear when the checkbox is checked.

I think the "Advanced Zip Url" panel could work well, as we could only show the panel when zip url is selected.

[liciavale]

sounds good! Thanks @dominiqueclarke

[liciavale]

@andrewvc @dominiqueclarke @drewpost I found this pattern that we could reuse here:

Wdyt?

[shahzad31]

i wasn't able to make zipurl configuration work while doing POST FF testing, inline scripe, and the script recorder format works pretty well for me.

Zip url without enable tls options and using default tls option, in both cases it didn't work for me.

[shahzad31]

Tested it again and this time it works, so Post FF Testing looks good !!