[CLIENT][JAVA] Added a loadOpenLineageJson(InputStream) method, and refactored the existing loadOpenLineageYaml(InputStream) method

[d-m-h]

Problem

The loadOpenLineageYaml(InputStream) method asked for YAML (via the method name), but it actually expected JSON via the method implementation.

Closes: #2487

Solution

1. Introduce a new method, called loadOpenLineageJson(InputStream) that expects and utilises JSON.
2. Refactor the old one, so it expects and utilises YAML.

Checklist

• You've signed-off your work
• Your pull request title follows our guidelines
• Your changes are accompanied by tests (if relevant)
• Your change contains a small diff and is self-contained
• Your comment includes a one-liner for the changelog about the specific purpose of the change (if necessary)
• You've added a header to source files (if relevant)

---

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2023 contributors to the OpenLineage project

[mobuchowski]

@d-m-h @pawel-big-lebowski do you think we can actually change name of OpenLineageYaml to something like OpenLineageConfig or it is too much of a breaking change?

[pawel-big-lebowski]

@d-m-h @pawel-big-lebowski do you think we can actually change name of OpenLineageYaml to something like OpenLineageConfig or it is too much of a breaking change?

@mobuchowski I think we can go for that. I cannot guarantee this will not cause issue for custom java client users, but this should have a moderate impact on Spark & Flink integration.

@d-m-h I really like the idea of fallback to JSON config if the yaml parsing fails 🥇

[d-m-h]

@d-m-h @pawel-big-lebowski do you think we can actually change name of OpenLineageYaml to something like OpenLineageConfig or it is too much of a breaking change?

I initially wanted to do that, but I decided on the split method approach and then the subsequent fallback approach, because I could not measure the impact.