[Monitoring] Change all configs to monitoring.*

[chrisronline]

Relates to #52639

This PR is the first step in supporting the new monitoring.* config settings, which will allow users to ship monitoring data directly to the monitoring cluster.

Due to limitations in the platform, the monitoring plugin can only support a single configPrefix, which currently is xpack.monitoring.*. If we want to support monitoring.* config settings in Kibana, we need to change the configPrefix for monitoring to monitoring.*, but we need to also migrate all the existing configs to use this new configPrefix.

This PR does that and also changes some of the hierarchy for the configs.

Below is a table of the changes:

Current	New
xpack.monitoring.ui.enabled	monitoring.ui.enabled
xpack.monitoring.max_bucket_size	monitoring.ui.max_bucket_size
xpack.monitoring.min_interval_seconds	monitoring.ui.min_interval_seconds
xpack.monitoring.show_license_expiration	monitoring.ui.show_license_expiration
xpack.monitoring.ui.container.elasticsearch.enabled	monitoring.ui.container.elasticsearch.enabled
xpack.monitoring.ui.container.logstash.enabled	monitoring.ui.container.logstash.enabled
xpack.monitoring.elasticsearch.hosts	monitoring.ui.elasticsearch.hosts
xpack.monitoring.elasticsearch.username	monitoring.ui.elasticsearch.username
xpack.monitoring.elasticsearch.password	monitoring.ui.elasticsearch.password
xpack.monitoring.ccs.enabled	monitoring.ui.ccs.enabled
xpack.monitoring.elasticsearch.logFetchCount	monitoring.ui.elasticsearch.logFetchCount
xpack.monitoring.kibana.collection.enabled	monitoring.kibana.collection.enabled
xpack.monitoring.kibana.collection.interval	monitoring.kibana.collection.interval
xpack.monitoring.xpack_api_polling_frequency_millis	monitoring.xpack_api_polling_frequency_millis
xpack.monitoring.cluster_alerts.email_notifications.enabled	monitoring.cluster_alerts.email_notifications.enabled
xpack.monitoring.cluster_alerts.email_notifications.email_address	monitoring.cluster_alerts.email_notifications.email_address
xpack.monitoring.tests.cloud_detector.enabled	monitoring.tests.cloud_detector.enabled

Note that both sets of configs will work after this PR - there is no breaking change here

[chrisronline]

@elasticmachine merge upstream

[elasticmachine]

user doesn't have permission to update head repository

[elasticmachine]

Pinging @elastic/stack-monitoring (Team:Monitoring)

[chrisronline]

cc @pickypg @ycombinator This is safe to release in a minor (as there is not a breaking change) but just want to validate the name changes if either of you have a chance to check it out

[pickypg]

@chrisronline I wonder if maybe stackMonitoring is better now, but it's also so long and awkward to type.

[chrisronline]

@pickypg That change would need to be consistent across the other stack products too, and it would mean changing the current beats config names (which have been available since 7.2 I think). I'm not necessarily opposed, but I'm not sure there is enough value.

[pickypg]

Sold on your reasoning.

[chrisronline]

@elasticmachine merge upstream

[elasticmachine]

user doesn't have permission to update head repository

[igoristic]

Looks good! 👍

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 75b0c8e

History

• 💔 Build #22863 failed 75bff65
• 💔 Build #22840 failed a1a6937
• 💚 Build #21468 succeeded 9876c22
• 💚 Build #21120 succeeded d676834
• 💚 Build #21078 succeeded f6ea96c

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

[chrisronline]

Backport:

7.x: aa2cb48