feat: Add dynamically emitted asset events to OpenLineage

[kacpermuda]

On Airflow 3, tasks can emit asset events at runtime in several ways beyond statically declaring inlets=/outlets= on the operator. Today OpenLineage only sees the static declarations - anything the task produces dynamically is invisible to OL unless a dedicated extractor or hook-lineage reader picks it up.

This PR closes this gap and adds those dynamic assets into:

• AirflowRunFacet.task.inlets / outlets — so the serialized task snapshot reflects what actually ran.
• The OL job's inputs / outputs datasets (the "no extractor, no hook lineage" fallback) - via the existing translate_airflow_asset converter, deduped by (namespace, name) against static inlets/outlets and against each other.

Static inlets / outlets behavior is unchanged. Dynamic assets are appended to the static ones; nothing static is dropped, replaced, or rewritten. If a task has no dynamic events, the emitted facet is identical to before.

Inlets are unaffected by this PR - Airflow has no runtime inlet_events emission path that adds new inlets, so the static list remains the source of truth on the input side.

There is also a small change to use ProvidersManagerTaskRuntime from task sdk instead of legacy ProvidersManager from core, as it's raising deprecation warning.

How users emit these events

1. Via AssetAlias + outlet_events (alias resolved at runtime):

@task(outlets=[AssetAlias("my-alias")])
def producer(*, outlet_events):
    outlet_events[AssetAlias("my-alias")].add(
        Asset("s3://bucket/file.txt"), extra={"rows": 42}
    )

-> OL outlet = "[{'uri': 's3://bucket/file.txt', 'extra': {'rows': '42'}, 'asset_type': 'asset_event_from_alias', 'source_alias': 'my-alias'}]"

2. Via outlet_events directly on a statically-declared Asset (no alias):

@task(outlets=[Asset("s3://bucket/file.txt")])
def producer(*, outlet_events):
    outlet_events[Asset("s3://bucket/file.txt")].extra = {"rows": 42}

-> OL outlet = "[{'uri': 's3://bucket/file.txt', 'extra': {'rows': 42}, 'asset_type': 'asset_event'}]"

3. Via yield Metadata(...) from the task:

@task(outlets=[Asset("s3://bucket/file.txt")])
def producer():
    yield Metadata(Asset("s3://bucket/file.txt"), extra={"rows": 42})

-> Same as .2 above

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

Generated-by: Claude following the guidelines

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[mobuchowski]

Some nits, no blockers.