…45960)

* feat(task_sdk): add support for inlet_events in Task Context

* feat(task_sdk): add AssetEventCollectionResponse

* refactor(task_sdk): combine asset event uris

* refactor(api_fastapi): extract asset_event datamodels from asset

* fix(task_sdk): revert unrelated datamodels change

* fix(task_sdk/context): add _get_asset_events_from_db for fixing tests

* test(task_sdk): add test cases for execution_time context inlet access

* test(task_sdk): extend test_handle_requests to include asset event calls

* test(execution_api): add tests to asset event apis

* fix(execution_api): remove unnecessary redact

* feat(task_sdk): extract asset response from asset event response

* feat(task_sdk): add missing http exception

* feat(task_sdk): extract asset response from asset event response

* feat(task_sdk): remove duplicate inlet logic

* feat(task_sdk): remove AssetEvent form definitions

* test(task_sdk): add test case test_run_with_asset_inlets

* docs(newsfragments): add description of how inlet_events access has been changed

…45960)

* feat(task_sdk): add support for inlet_events in Task Context

* feat(task_sdk): add AssetEventCollectionResponse

* refactor(task_sdk): combine asset event uris

* refactor(api_fastapi): extract asset_event datamodels from asset

* fix(task_sdk): revert unrelated datamodels change

* fix(task_sdk/context): add _get_asset_events_from_db for fixing tests

* test(task_sdk): add test cases for execution_time context inlet access

* test(task_sdk): extend test_handle_requests to include asset event calls

* test(execution_api): add tests to asset event apis

* fix(execution_api): remove unnecessary redact

* feat(task_sdk): extract asset response from asset event response

* feat(task_sdk): add missing http exception

* feat(task_sdk): extract asset response from asset event response

* feat(task_sdk): remove duplicate inlet logic

* feat(task_sdk): remove AssetEvent form definitions

* test(task_sdk): add test case test_run_with_asset_inlets

* docs(newsfragments): add description of how inlet_events access has been changed

…context key for Airflow 3.0 (`AIR301`) (#22850)

## Summary

<!-- What's the purpose of the change? What does it do, and why? -->
Context:
apache/airflow#41641

1. apache/airflow#45961
* <strike>create_dagrun removed from airflow...DAG</strike> (This has
already been implemented in AIR301)
* context key dag_run.external_trigger removed
2. apache/airflow#45960
* context["inlet_events"]["url"] → context["inlet_events"][Asset("url")]
3. apache/airflow#41348
* context key triggering_dataset_events → triggering_asset_events

The existing AIR301 rules can detect when users access a removed key
such as `execution_date` through Airflow's `context`. For example,
`context["execution_date"]`, or `context["dag_run"]`. However, if an
attribute is deprecated from a context key, such as
`context["dag_run"].external_trigger`, the current implement will not
flag it.

This PR adds the logic for such check, and add two rules to flag the
deprecated attribute for the `"dag_run"` and `"inlet_events"` context
key. In addition to this, `"triggering_dataset_events"` is a deprecated
context key which can be handled by the existing rule. However, the
existing rule doesn't raise a diagnostic. Hence, the rule logic is
refactored a little bit, such that we can add this check and suggest a
`Replacement::Rename`.

## Test Plan

<!-- How was it tested? -->
The test cases have been added to `AIR301_context.py`, and all the tests
have been run locally and success. @Lee-W , could you please review it
when you have time, thanks!

## Notes

In #22376, we introduced some
improvements to the AIR301 code. I will re-base this PR when we are all
good on that, so it can pick up those code structure improvements, and
updated rules.