Plugins that depend on support-core and use snakeyaml are getting exceptions like the following:

java.lang.NoSuchMethodError: org.yaml.snakeyaml.events.MappingStartEvent.<init>(Ljava/lang/String;Ljava/lang/String;ZLorg/yaml/snakeyaml/error/Mark;Lorg/yaml/snakeyaml/error/Mark;Ljava/lang/Boolean;)V

Using snakeyaml without shading it is a little precarious in the current Jenkins ecosystem, see the comments in JENKINS-50202 for more details.

Support-core has a transitive dependency on snakeyaml through the javafaker library, which was added as part of support bundle anonymization.

My proposal is to replace javafaker with wordnet-random-name. It doesn't allow us to use different themes for different kinds of data, but it has no compile-scope dependencies.
We could also downgrade to snakeyaml 1.17 to avoid API compatibility issues for now (assuming javafaker 0.15 is compatible with snakeyaml 1.17), or we could shade it and the javafaker library to avoid conflicts with other plugins, but getting rid of it seems like the easiest long-term solution.