[Synthetics] Remove auto creation of Synthetics monitor status default rule

[dominiqueclarke]

Currently, Synthetics auto creates a single monitor status rule that applies to all monitors.

https://github.com/elastic/kibana/pull/186585 will introduce the ability to further customize the Synthetics monitor status rule.

Once merged, we want to remove this auto creation mechanism entirely in favor of deliberate user opt in.

• [ ] The default monitor status and tls rules should no longer be created when the user visits the Synthetics app
• [ ] In the Settings view, the toggles to enable and disable the rule should be removed
• [ ] References to the status/tls rule enabled settings (defaultStatusRuleEnabled and defaultTlsRuleEnabled) within the Synthetics saved object should be removed from the code base, particularly from the default_alert_service.ts file.
• [ ] Default rules, both TLS and Monitor Status, should be able to be enabled/disabled and deleted from the Rule management page
• [ ] If a Synthetics monitor status rule is not present, either the default or a custom rule, a callout should be displayed on the Synthetics overview page with a call to action button to create either the default alert or a custom alert.
• [ ] If the default TLS rule is not present, the callout should also include a call to action to create a TLS rule

[elasticmachine]

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

[justinkambic]

Is there a planned CTA for alerting once a monitor is created, now that we won't automatically cover all monitors by default?