[Bug]: Parse YAML ExpansionService configs directly using SnakeYAML

[chamikaramj]

What happened?

Currently, YAML ExpansionService config files are parsed using the Jackson YAML binding (which uses SnakeYAML underneath).

But it seems like the versions of Jackson and SnakeYAML used by Beam conflict with each other causing a failure.

To address this we could directly parse YAML files using SnakeYAML.

Upgrading Jackson might be a fix as well but this is more involved.

There's more info here: #26743 (comment)

Issue Priority

Priority: 1 (data loss / total loss of function)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner