Move `checkShards` from Deprecation API to Health API

[HiDAl]

What?

Currently, in order to upgrade a cluster to a newer version, a set of checks are run validating that it's safe to upgrade. One of these checks validates that there's enough room in the cluster to create new shards for (potential) intermediate indices.

How

The main idea it creates a new indicator into the new Health API, in such a way it'll be displayed on the Deployment Management > Monitoring > Health page. Later, the Cluster Upgrade Tool should use this indicator to validate that upgrading the cluster is safe. Also, the check should be removed from the Deprecation API.

Tasks

• Talk with the UI team to confirm that the new indicator, once exposed in the UI, will automatically appear in the UI or it must be developed involved
• Create all the machinery in Elasticsearch repo to expose the new Health API indicator (ticket tracking this work [HealthAPI] Warn when max shards per node setting is reached #91119)
• Start the conversations with the Cloud team about the needed changes on their side to use this indicator –or any other new indicator– to block upgrades in case the cluster is Unhealthy.
• Removes the old check from the Deprecation API remove ClusterDeprecationChecks.checkShards code #95177

Related

• PR introducing the check Adding a deprecation info API check for too many shards #85967

[elasticsearchmachine]

Pinging @elastic/es-data-management (Team:Data Management)

[HiDAl]

Added a new task after the conversations with @ElenaStoeva and @sabarasaba in order of display the new indicator