Do not return different exceptions when connections arent found for AF3 and AF2 #52880
Description
Body
A classic occurrence for this is here: #52838
The fact that we have to handle v3 exceptions separately from v2, makes it hard for providers to migrate to task sdk in its entirety hard too.
Merge these 2 paths into one and return the classic exception: AirflowNotFoundException for such cases while retrieving connections.
Potentially could be an issue with variables too, which can be handled separately once I analyse that.
Committer
- I acknowledge that I am a maintainer/committer of the Apache Airflow project.