Investigate if we can optimise register_asset_changes_in_db from task runner

### Body Right now, for registering asset events on task completion, we send across a lot of "events" for AssetNameRef and AssetUriRef types. Maybe we can optimise it by retrieving the Asset directly using client APIs and sending those. This will also simplify `register_asset_changes_in_db` ### Committer - [x] I acknowledge that I am a maintainer/committer of the Apache Airflow project.