Adding 'invocation_id' to run-results as expected by OL

[amoghrajesh]

Openlineage released 1.34.0:

> openlineage-integration-common==1.34.0
> openlineage-python==1.34.0
> openlineage_sql==1.34.0

This causes a breaking change in OpenLineage 1.34.0 where the DBT processor expects an invocation_id field in the run metadata, but the test data didn't include this field.

Added the invocation_id field to the metadata section of the test run_results.json file and assigned it equal to run_id:

{
  "metadata": {
    "dbt_schema_version": "https://schemas.getdbt.com/dbt/run-results/v4.json",
    "dbt_version": "1.6.1",
    "invocation_id": "188471607"
  }
}

Fixes CI:

______ TestGenerateOpenLineageEventsFromDbtCloudRun.test_generate_events _______
[gw2] linux -- Python 3.9.23 /usr/local/bin/python3
providers/dbt/cloud/tests/unit/dbt/cloud/utils/test_openlineage.py:187: in test_generate_events
    generate_openlineage_events_from_dbt_cloud_run(mock_operator, task_instance=mock_task_instance)
providers/common/compat/src/airflow/providers/common/compat/openlineage/check.py:100: in wrapper
    return func(*args, **kwargs)
providers/dbt/cloud/src/airflow/providers/dbt/cloud/utils/openlineage.py:192: in generate_openlineage_events_from_dbt_cloud_run
    events = processor.parse().events()
/usr/local/lib/python3.9/site-packages/openlineage/common/provider/dbt/processor.py:201: in parse
    events += self.parse_execution(context, nodes)
/usr/local/lib/python3.9/site-packages/openlineage/common/provider/dbt/processor.py:299: in parse_execution
    self.get_run(run_id),
/usr/local/lib/python3.9/site-packages/openlineage/common/provider/dbt/processor.py:685: in get_run
    "dbt_run": self.dbt_run_run_facet(),
/usr/local/lib/python3.9/site-packages/openlineage/common/provider/dbt/processor.py:704: in dbt_run_run_facet
    return DbtRunRunFacet(invocation_id=self.run_metadata["invocation_id"])  # type: ignore[index]
E   KeyError: 'invocation_id'

Example failure: https://github.com/apache/airflow/actions/runs/15748852234

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[kacpermuda]

LGTM, It's caused by OpenLineage/OpenLineage#3738, now we're including invocation_id in DBT facets. @dolfinus am I assuming correctly that it's always in the metadata returned by DBT?

[dolfinus]

According to https://github.com/dbt-labs/dbt-core/pull/4340/files#diff-33c94e40283afdfeba411a98c0628fc610c287e41c3477d88559f1e0244259c3R317, invocation_id is a part of manifest since dbt-core 1.0.0.
But in manifest schema https://github.com/dbt-labs/dbt-core/blob/main/schemas/dbt/manifest/v12.json this field is marked as nullable. Let's make it optional OpenLineage/OpenLineage#3796