[airflow] Get rid of Replacement::Name and replace them with Replacement::AutoImport for enabling auto fixing (AIR301, AIR311)

[Lee-W]

Summary

Similiar to #17941.

Replacement::Name was designed for linting only. Now, we also want to fix the user code. It would be easier to replace it with a better AutoImport struct whenever possible.

On the other hand, AIR301 and AIR311 contain attribute changes that can still use a struct like Replacement::Name. To reduce the confusion, I also updated it as Replacement::AttrName

Some of the original Replacement::Name has been replaced as Replacement::Message as they're not directly mapping and the message has now been moved to help

Test Plan

The test fixtures have been updated

[github-actions]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

ℹ️ ecosystem check detected linter changes. (+2 -2 violations, +0 -0 fixes in 1 projects; 54 projects unchanged)

apache/airflow (+2 -2 violations, +0 -0 fixes)

ruff check --no-cache --exit-zero --ignore RUF9 --no-fix --output-format concise --preview --select ALL

+ providers/fab/tests/unit/fab/auth_manager/api_fastapi/conftest.py:27:26: AIR301 `appbuilder` is removed in Airflow 3.0
- providers/fab/tests/unit/fab/auth_manager/api_fastapi/conftest.py:27:26: AIR301 `appbuilder` is removed in Airflow 3.0; The constructor takes no parameter now
+ providers/fab/tests/unit/fab/auth_manager/test_fab_auth_manager.py:99:26: AIR301 `appbuilder` is removed in Airflow 3.0
- providers/fab/tests/unit/fab/auth_manager/test_fab_auth_manager.py:99:26: AIR301 `appbuilder` is removed in Airflow 3.0; The constructor takes no parameter now

Changes by rule (1 rules affected)

code	total	+ violation	- violation	+ fix	- fix
AIR301	4	2	2	0	0

[ntBre]

This looks good to me, just one question!

[ntBre]

Do these need to be separate? It looks like all of the Replacement::Messages down below include Use ... instead in their messages, so I think you could at least combine these match arms if not the entire variants.

Suggested change

	Replacement::AttrName(name) => Some(format!("Use `{name}` instead")),
	Replacement::Message(message) => Some((*message).to_string()),
	Replacement::AttrName(name) | Replacement::Message(name) => Some(format!("Use `{name}` instead")),

Or do you have plans to make the messages more different later on?

[Lee-W]

There are one or two exceptions now. So it's still needed

ruff/crates/ruff_linter/src/rules/airflow/rules/removal_in_3.rs

Lines 717 to 719 in 8cbd433

	["decorators", "apply_defaults"] => Replacement::Message(
	"`apply_defaults` is now unconditionally done and can be safely removed.",
	),

I'm thinking of merging the message into other types later on so that we can provide extra information for them as well.

[ntBre]

Ah thanks, I missed that one. I'll merge this!