Add snakeyaml dependency back in

[georgew5656]

Description

While doing some testing on my other PR (#14030) with the new fabric8 library version, I noticed some snakeyaml error when starting up the overlord. We need to add the snakeyaml library into the pom still as fabric8 6.4.1 still depends on it

This PR has:

• [X ] been self-reviewed.
  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
• added documentation for new or modified features or behaviors.
• a release note entry in the PR description.
• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
• added or updated version, license, or notice information in licenses.yaml
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• added integration tests.
• [X ] been tested in a test Druid cluster.

[nlippis]

🏎️

[clintropolis]

the dependency checker part of ci seems to be complaining that this dependency is not used, should we just ignore it?

[INFO] --- maven-dependency-plugin:3.1.1:analyze (default-cli) @ druid-kubernetes-overlord-extensions ---
Warning:  Unused declared dependencies found:
Warning:     org.yaml:snakeyaml:jar:1.33:compile

[georgew5656]

the dependency checker part of ci seems to be complaining that this dependency is not used, should we just ignore it?

[INFO] --- maven-dependency-plugin:3.1.1:analyze (default-cli) @ druid-kubernetes-overlord-extensions ---

Warning:  Unused declared dependencies found:

Warning:     org.yaml:snakeyaml:jar:1.33:compile

let me check if updating the version will help, i can see what version of snakeyaml fabric8 uses exactly

[nlippis]

Let's hold off on this change. The reason to put it in was so that the snakeyaml dependency would be included in the bundle. Adding this into the pom does not seem to fix that.