[SPARK] support builtin lineage within DatasourceV2Relation

[pawel-big-lebowski]

Problem

Support builtin lineage within DatasourceV2Relation

Related to: #2349

Solution

Extensions can include openlineage related properties within table member of DatasourceV2Relation nodes of a job logical plan. PR contains logic to extract the properties and convert them into dataset facets.

Note: All schema changes require discussion. Please link the issue for context.

• Your change modifies the core OpenLineage model
• Your change modifies one or more OpenLineage facets

If you're contributing a new integration, please specify the scope of the integration and how/where it has been tested (e.g., Apache Spark integration supports S3 and GCS filesystem operations, tested with AWS EMR).

One-line summary:

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
• You've updated any relevant documentation (if relevant)
• Your comment includes a one-liner for the changelog about the specific purpose of the change (if necessary)
• You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
• 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]

One comment regarding documentation, looks good to me besides that

[mobuchowski]

Please explain that customFacet will be a key that the facet will be attached to inside of the facets dictionary in resulting event JSON:

inputs: [{
    "name": "dataset.schema.name",
    "namespace": "bigquery",
    "facets": {
        "customFacet": {
            "property": "value"
            ...
        }
    "
}}

Also, shouldn't OpenLineage side add _producer? I doubt those custom facets would add _schemaURL too, but that'a another topic.