Use canonical exception paths in task sdk

[amoghrajesh]

---

Was generative AI tooling used to co-author this PR?

• No

These exceptions are present in task sdk already and only backcompat is in airflow.exceptions, we should use the canonical paths instead of older paths.

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[amoghrajesh]

cc @Dev-iL with regards to: #60278