[airflow] Add AIR331 rule for airflow.traces module removed in Airflow 3.2

[dstandish]

Hi -- I am an airflow contributor. A real human one.

I want to add this rule to help identify if an airflow user is importing from the traces package (which we are removing in 3.2).

Thanks for your review.

Summary

• Add new AIR331 lint rule that flags imports from the airflow.traces module, which was removed in Airflow 3.2
• Covers airflow.traces.otel_tracer, airflow.traces.tracer, airflow.traces.utils, and all submodule members
• Includes test fixtures and snapshot tests

Test plan

• Added test fixture AIR331_names.py with positive and negative cases
• Snapshot tests verify correct diagnostics are emitted

[ntBre]

Thank you! I'm happy to give this a review, but I like to check in with @Lee-W first :)

[astral-sh-bot]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

[Lee-W]

Sure, will do it early next week. We're establishing the process how we contribute to ruff from airflow community. But Daniel's PR is most likely correct haha. Will take a deeper look 👀

[dstandish]

Sure, will do it early next week. We're establishing the process how we contribute to ruff from airflow community. But Daniel's PR is most likely correct haha. Will take a deeper look 👀

All credit goes to claude

[dstandish]

@Lee-W if we are also removing airflow.metrics and airflow.stats in 3.2, would it make sense to add these to the same ruff rule?

[Lee-W]

@Lee-W if we are also removing airflow.metrics and airflow.stats in 3.2, would it make sense to add these to the same ruff rule?

yep, we group logics with the same purpose into one rule