[OpenLineage] fix: Fix parent id macro and remove unused utils

[kacpermuda]

Source of this PR is here, thanks @blacklight.

When using lineage_parent_id, a user should receive all the information needed to create ParentRunFacet. Now we have this as lineage_parent_id function:

airflow/airflow/providers/openlineage/plugins/macros.py

Lines 60 to 66 in 30f7b2a

	job_name = OpenLineageAdapter.build_task_instance_run_id(
	dag_id=task_instance.dag_id,
	task_id=task_instance.task.task_id,
	execution_date=task_instance.execution_date,
	try_number=task_instance.try_number,
	)
	return f"{_JOB_NAMESPACE}/{job_name}/{run_id}"

So as a job name, we get the UUID instead of dag_id.task_id. After the change, we will be able to easily create ParentRunFacet:

parent_id = lineage_parent_id(task_instance)
parent_namespace, parent_job_name, parent_run_id = parent_id.split("/")
parent_run_facet = ParentRunFacet.create(parent_run_id, parent_job_name, parent_namespace)

Also, we are extracting the namespace again in macros module, when we have one already extracted in adapter module, and this one is used in events so we should use the same one here.

Important

I am not sure if removing the run_id from the macro is a breaking change. We could probably leave it there, but there is no real use in it i think.

---

^ 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 newsfragments.

[blacklight]

LGTM - if this PR extends mine shall I proceed with closing the other one?

[kacpermuda]

if this PR extends mine shall I proceed with closing the other one?

This one is for the provider package, and yours is for openlineage-airflow package, so we can proceed with both 😄