[fix][sec] Update dependencies to use snakeyaml 2.0 against 3.0

[eugene-cheverda]

Fixes #20224

Motivation

Fixes https://avd.aquasec.com/nvd/cve-2022-1471 caused by snakeyaml by updating all dependencies bringing it into the project

Modifications

Updated jackson, snakeyaml and prometheus dependencies, updated code to use non-deprecated EnumResolver functions

Verifying this change

• Make sure that the change passes the CI checks.

This change is already covered by existing tests, such as FieldParserTest.

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

If the box was checked, please highlight the changes

• Dependencies (add or upgrade a dependency)
• The public API
• The schema
• The default values of configurations
• The threading model
• The binary protocol
• The REST endpoints
• The admin CLI options
• The metrics
• Anything that affects deployment

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

Matching PR in forked repository

PR in forked repository: eugene-cheverda#2

[mattisonchao]

There's a corner regression by Jackson 2.15. It will affect our json schema. We will need to talk about it this in the dev mail list.
FasterXML/jackson-databind#3874

[mattisonchao]

@codelipenghui @Technoboy- @lhotari @michaeljmarshall @tisonkun would you mind taking a look?

[dave2wave]

I don't know if we would have the same concern in Pulsar, but jclouds attempted this upgrade and had to revert it.
apache/jclouds@cf4a926

[eugene-cheverda]

Hi @dave2wave

In my PR on master eugene-cheverda#1 I had successful runs of CI with this change, also the discussion on update to jackson 2.15.0 is held here.

[github-actions]

The pr had no activity for 30 days, mark with Stale label.

[tisonkun]

Covered by #20085.

[tisonkun]

Covered by #20085.

No. They are different issue.

[github-actions]

The pr had no activity for 30 days, mark with Stale label.

[lhotari]

@eugene-cheverda does this PR still apply?