New REST API endpoints for assets

[Lee-W]

Description

User Presentation Considerations

• [ ] /public/assets changes
  • [x] Use id as detail identifier in URL https://github.com/apache/airflow/pull/44801
  • [ ] Ability to search asset with name and/or uri (maybe name_pattern and uri_pattern are enough?)
  • [ ] Change aliases in AssetResponse to use only the id or name?
• [x] /public/assets/aliases https://github.com/apache/airflow/pull/44777
• [x] /public/assets/aliases/{id} https://github.com/apache/airflow/pull/44803
• [ ] /public/assets/{id}/materialize

Use case/motivation

Rationale

Related issues

No response

Are you willing to submit a PR?

• [X] Yes I am willing to submit a PR!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[uranusjr]

The two subitems under /public/assets/ are deferred for now until the UI folks start implementing. We’ll figure out if we need them and what exactly at the point.

[sunank200]

As per discussion with TP, we will pick up /public/assets/{id}/materialize once the POC with partitioning strategy change with the execution date is clear.

[phanikumv]

/public/assets/{id}/materialize will be picked up post https://github.com/apache/airflow/issues/46192

[uranusjr]

Working on this now that asset-triggered runs have the new logical date behaviour.