Allow Asset decorator to work with any TaskFlow operator

[yoeo]

closes: #51228

---

Extends the Airflow 3 @asset decorator to support any TaskFlow operator.
To match the Asset-Centric Syntax specification, the asset is implicitly set as an outlet of the that task it decorates.

This is my first contribution here, I tried to keep the changes to a minimum but please let me know if there are any issues, and I will do my best to address them.

Thanks.

---

Examples usage (from #51228 ):

from airflow.sdk import asset, task


# Asset generated by a PythonOperator task with extra arguments
# The task `outlets` argument is implicitly set to `[secret_data]`
@asset(schedule="@daily")
@task(doc="Generate a secret number", retries=3)
def secret_data():
    return 42


# Asset generated by a BashOperator task (supports extra arguments as well)
# The task `outlets` argument is implicitly set to `[write_data]`
@asset(schedule=secret_data)
@task.bash()
def write_data(ti):
    random_number = ti.xcom_pull(
        dag_id="secret_data",
        task_ids="secret_data",
        key="return_value",
        include_prior_dates=True,
    )
    return f"echo {random_number}"

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: [email protected]
  Slack: https://s.apache.org/airflow-slack

[Lee-W]

the test failure doesn't look like something related to this change. let me rebase from the main branch and see how it works

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.