Allow filtering hook-collected assets in OpenLineage emission policy

[ramitkataria]

Hook-level lineage registers an output asset for every object a hook writes, so a task that writes many objects reports one asset per object. The existing hook_lineage control is all-or-nothing: suppressing the noisy assets also loses the ones worth tracking from the same hook, and the collector cannot tell the two apart once its assets are read as one set.

Filtering by asset URI or reporting hook class lets a Dag keep the lineage that matters while dropping the noise, and doing it where hook lineage is consumed covers every instrumented hook at once rather than one provider at a time.

Note this reduces what gets reported rather than what gets collected, so it does not recover assets already dropped by max_assets_per_collector.

closes: #63371

cc @SamWheating @kacpermuda @ashb @vincbeck @shnhdan @eladkal @mobuchowski

---

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

• Yes (please specify the tool below)

---

• 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.