Support templated extra in outlets assets

[hussein-awala]

This PR adds support for Jinja templates in outlet assets, which will be rendered in the emitted events.

---

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

[Lee-W]

one question, one nit. no major issue on my end

[vikramkoka]

Not an issue, but a question: What's the intended use case here?

[hussein-awala]

Not an issue, but a question: What's the intended use case here?

The asset can be used to connect two DAGs for two different teams. The owner of the dataset (the team who owns the producer task) is responsible for providing some metadata to the consumer DAG to explain what to process and how.

To simplify the answer, I can take a part of AIP-76 as an example. With this PR, the partition can be defined at runtime, since we can have backfills and runs created by external events, and the partition is not always known at parse time.

SomeOperator(
    task_id="write_asset",
    ...,
    outlets=Asset(
        "asset_example",
        extra={
            "partition": "{{ logical_date.strftime('%Y_%m_%d/%H') }}",
        }
    ),
)

Also, when the team owner of the dataset wants to change the partition pattern, there’s no need to notify the consumer side, as the dataset schema still respects the data contract.