[FLINK-27420] Recreate metric groups for each new RM to avoid metric loss

[baugarten]

See #19607

This is the same PR, but based on release-1.15. This appears safe to cherry-pick to release-1.14 as well (azure). I can open another PR for 1.14 if that's preferable.

What is the purpose of the change

Fix bug identified in https://issues.apache.org/jira/browse/FLINK-27420 by recreating the metric groups for slot manager and resource manager when leadership is granted.

Brief change log

• The MetricRegistry and Hostname are stored in the ResourceManagerProcessContext
• The SlotManagerMetricGroup and ResourceManagerMetricGroup are created in the ResourceManagerFactory

Verifying this change

• Added tests for granting leadership, revoking leadership, and granting leadership again and verifying the metrics are registered. I verified this test fails before the patch. Verified this test passes locally
• Currently running azure pipelines: https://dev.azure.com/baugarten0115/baugarten-flink/_build/results?buildId=76&view=results

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: yes
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

[flinkbot]

CI report:

• 61df03b Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[xintongsong]

@baugarten,
It seems we still have some compiling issues for 1.14, most likely related to the Junit 4->5 migration which starts in 1.15.

I'll merge this PR for the 1.15 branch.

[xintongsong]

fbc8e46