Summary

This PR removes the latency warnings one would get when exceeding the minimum latency in the monitor management UI.

It complements the work we had previously done for https://github.com/elastic/synthetics-service/issues/324. It also adds work on top of #127961.

In the previous cloud/synthetics meeting we have decided we would scrape these warnings because latency doesn't actually impact the platform's usage so we don't need to apply a minimum.

PS: I've added this PR to the board so that we can be sure we have done Post-FF testing on it, not only on the first one. I've also updated the previous PR with a link to this one to be sure people will be testing the right thing.

Given we're removing functionality that shouldn't be there, I've also added the bug label to this.

How to test this PR Locally

1. Create a new manifest.json with the following content and place it under a folder named, for example, manifest_folder.
   ⚠️ Notice there's no latency limits here.

   {
     "throttling": {
       "downloadBandwidthLimit": 20,
       "uploadBandwidthLimit": 10
     },
     "locations": {
       "Local Synth Node [MANIFEST]": {
         "url": "https://localhost:10001",
         "geo": {
           "name": "Example - Local",
           "location": {"lat": 41.25, "lon": -95.86}
         },
         "status": "beta"
       }
     }
   }

2. Run an HTTP server to serve the contents of the manifest_folder

   $ npx http-server manifest_folder --port 8082
   

3. In Kibana's config, fill the following options:

   # Make sure your pods will be able to send data to ES which should be bound to your host's 9200 port
   xpack.uptime.service.hosts: [http://host.docker.internal:9200]
   
   # Add the URL for the manifest with the `throttling` configs you're serving
   xpack.uptime.service.manifestUrl: http://localhost:8082/manifest.json
   
   # Make sure to disable the devUrl so you're only fetching locations from the `manifest` as we'll do in production
   # xpack.uptime.service.devUrl: https://localhost:10001
   
   # Enable the Monitor Management UI
   xpack.uptime.ui.monitorManagement.enabled: true

4. Run the service locally

   $ DEV=true LOGLEVEL=trace CACERTFILE=./k8s/cert-test/build/bundle.pem SERVERCERT=./k8s/cert-test/build/local-server.pem SERVERKEYFILE=./k8s/cert-test/build/local-server.key PORT=10001 ./synthetics-service
   

5. Run Kibana and try to add a monitor. You should see the warnings above when exceeding the limits defined in your manifest.json file.
   You should be able to set latency values to any value and shouldn't see a warning.
6. Disable throttling and you should see a warning about the automatic caps.
7. Create a monitor with a particular throttling value set and save it. Use the following code for that monitor:

   step("load homepage", async () => {
       await page.goto('https://www.fast.com');
   });
   
   step("wait for test", async () => {
     await page.waitForSelector('#show-more-details-link');
     await page.waitForTimeout(10000);
     await page.click("#show-more-details-link");
   });
   
   step("wait for up/lat", async () => {
     await page.waitForSelector(".extra-measurement-value-container.succeeded");
     await page.waitForTimeout(10000);
   });

8. Wait for that monitor to run and ensure your throttling values have been applied.
9. Create a monitor with throttling disabled using the same script as above and confirm that your script has not been throtted.
   ⚠️ It will be throttled on the service because of platform limits.
10. Create a monitor with throttling values which exceed the limits for the node. You should still be able to save such monitors.

⚠️ You should not be able to see these warnings in the Fleet UI.

Checklist

Delete any items that are not applicable to this PR.

• Unit or functional tests were updated or added to match the most common scenarios (actually I removed some that were unnecessary)
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately