[Synthetics] Add error handling for private locations

[dominiqueclarke]

Summary

Related to elastic/uptime#475

Adds better error handling for synthetics private locations.

When adding a monitor

Ensures that when downstream actions related to private locations fail, the monitor saved object does not save

When editing a monitor

Ensures that when downstream actions related to private locations fail, the monitor is not updated

When deleting a monitor

Ensures that when downstream actions related to private locations fail, the monitor is not deleted

Testing

I tested this PR by adding deliberate errors, such as reference issues, to the synthetics_private_location file, including the deleteMonitor, createMonitor, and editMonitor code paths.

1. Add errors to the createMonitor code
2. Navigate to the Uptime, create a private location, then attempt to create a monitor with a private location
3. An error toast should appear
4. Navigate to the Uptime monitor list. Ensure the monitor was not saved.
5. Add errors to the editMonitor code
6. Navigate to the Uptime, create a monitor without a private location. It should work successfully.
7. Update that monitor by adding a new private location.
8. An error toast should appear
9. Navigate to the Uptime monitor list. Ensure the monitor was not updated and the new location does not appear to be saved
10. Remove the error from createMonitor code
11. Create a monitor with a private location. It should go through successfly.
12. Add an error to the deleteMonitor code.
13. Attempt to delete the monitor with the private location.
14. An error toast should appear.
15. Ensure the monitor is not deleted

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

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[dominiqueclarke]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: b37905e
• Storybooks Preview

Metrics [docs]

✅ unchanged

History

• 💔 Build #60933 failed 5fe9eca
• 💚 Build #60856 succeeded 876aab2
• 💔 Build #60797 failed 642f185
• 💔 Build #60684 failed f5bb4ad
• 💔 Build #60544 failed 7ade6ea

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[lucasfcosta]

Post-FF testing LGTM!

I did receive an error when trying to save the monitor after adding errors to its code.

Once I removed the error and saved it, editing with errors caused the monitor not to be edited, as expected.

Finally, deleting also didn't delete the saved object once I added errors to it.