Register and schedule Micrometer MeterRegistry when Meters are registered

[eyalkoren]

What does this PR do?

As reported in spring-projects/spring-boot#26630, premature initialization of Micrometer's MeterRegistry in Spring applications may cause metrics loss.
This PR attempts to work around this issue assuming that Meters are only registered to fully initialized meter registries.
This assumption is yet to be verified.

Checklist

• This is a bugfix
  • I have updated CHANGELOG.asciidoc
  • I have added tests that would fail without this fix
  • I verified the described issue is resolved using this fix where it is reproducible without this fix
  • I upgraded Micrometer dependency to latest and updated dependabot.yml so that we continuously test against the latest version
  • I added a MicrometerInstrumentationVersionsIT to test with version 1.0.1

[apmmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2021-11-23T12:39:17.748+0000

• Duration: 74 min 39 sec

• Commit: fec7104

Test stats 🧪

Test	Results
Failed	0
Passed	2546
Skipped	21
Total	2567

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run benchmark tests : Run the benchmark test.

• run compatibility tests : Run the JDK Compatibility test.

• run integration tests : Run the APM-ITs.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[SylvainJuge]

LGTM, should be good as it has been validated in the field.

[SylvainJuge]

[minor] Was this change required due to upgrading micrometer that have different behavior between 1.0.1 and 1.8.0 or due to the change of instrumented method ?

[eyalkoren]

It's a different behavior - in the new version the abstract meters capture exceptions quietly, so we don't get to see that they failed