Make Airflow error messages more specific, clear and actionable

[omkar-foss]

Description

As per users' feedback in the Airflow Debugging Survey 2024, around 41.7% respondents don't consider error messages as actionable. Overall feedback also suggests that users find some error messages vague and confusing.

Use case/motivation

Goals for this issue are the following:

• Identify and revise error messages that are vague, lack context, or do not provide clear guidance on resolving issues.
• Provide detailed information, context, and actionable steps within the error messages to help users troubleshoot.
• Transform error messages with meaningful linking wherever possible. e.g. an error like Celery command failed on host can be transformed or displayed with something like "Please check your DAG processor timeout variable for this". So the user has a starting point to start debugging.

Related issues

Parent Issue: https://github.com/apache/airflow/issues/40975

Are you willing to submit a PR?

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

Code of Conduct

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