Ignore dynamic settings specified by deprecation.skip_deprecated_settings in node deprecation checks

[masseyke]

This commit makes it so that the NodeDeprecationChecks part of the deprecation info API will ignore settings
specified by deprecation.skip_deprecated_settings, even if those settings are dynamically set.
Closes #82889

[elasticmachine]

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

[dakrone]

I left a comment, I think we can do this without opening up the Metadata constructor or making a subclass

[masseyke]

In addition to the unit test, I did the following:
I brought up a new 7.17.0-SNAPSHOT cluster with this in its elasticsearch.yml:

deprecation.skip_deprecated_settings:
 - "discovery.zen.minimum_master_nodes"

I added two deprecated dynamic properties (but only one is listed in deprecation.skip_deprecated_settings):

PUT /_cluster/settings
{
  "transient": {
    "discovery.zen.minimum_master_nodes": "2"
  }
}

PUT /_cluster/settings
{
  "transient": {
    "discovery.zen.commit_timeout": "40s"
  }
}

Then I did

GET _migration/deprecations

And only discovery.zen.commit_timeout came back, as expected.

[dakrone]

LGTM, thanks Keith!

[jakelandis]

@masseyke - Thank you for the fast turn around time !