Set Snakeyaml to 1.33 in parent pom

[stianst]

We actually have 6 different versions of Snakeyaml throughout:

 - 1.33 [LATEST] (from org.keycloak:keycloak-quarkus-server)
 - 1.32 (from com.openshift:openshift-restclient-java)
 - 1.29 (from com.github.ua-parser:uap-java)
 - 1.27 (from org.springframework.boot:spring-boot-starter:2.4.13)
 - 1.26 (from com.github.ua-parser:uap-java)
 - 1.19 (from org.springframework.boot:spring-boot-starter:2.0.5)

This sets the version in the parent pom to align everything to one version

Closes #15339

[abstractj]

@stianst +1 about those changes. But I believe we need to think together about efficient ways to ban some 3rd party dependencies, like @pedroigor suggested with https://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html.

For example, updating SnakeYAML to 1.33 will solve a couple of CVEs, on the other hand release 1.33 already has a new CVE (https://snyk.io/blog/unsafe-deserialization-snakeyaml-java-cve-2022-1471) but maintainers didn't provide a new release.

More details:

• https://snyk.io/blog/unsafe-deserialization-snakeyaml-java-cve-2022-1471/
• https://bitbucket.org/snakeyaml/snakeyaml/commits/2b8d47c8bcfd402e7a682b7b2674e8d0cb25e522
• https://bitbucket.org/snakeyaml/snakeyaml/issues/561/cve-2022-1471-vulnerability-in
• https://bitbucket.org/snakeyaml/snakeyaml/pull-requests/39

[stianst]

@abstractj I agree with the banning of dependencies, but that's certainly a follow-up and not something to cover in this issue

[abstractj]

LGTM