[flake8-logging] Stabilize exc-info-outside-except-handler (LOG014)

[ntBre]

Summary

• Stabilizes LOG014 (exc-info-outside-except-handler) rule by changing it from Preview to Stable

Test plan

• ✅ Rule is already tested in main test function, no migration needed
• ✅ make check passes
• ✅ make test passes

Rule Documentation

• Test file
• Rule documentation

[github-actions]

ruff-ecosystem results

Linter (stable)

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

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

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

+ airflow-core/src/airflow/api_fastapi/execution_api/app.py:187:55: LOG014 `exc_info=` outside exception handlers
+ task-sdk/src/airflow/sdk/execution_time/supervisor.py:1027:13: LOG014 `exc_info=` outside exception handlers

apache/superset (+13 -0 violations, +0 -0 fixes)

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

+ superset/commands/report/base.py:106:75: LOG014 `exc_info=` outside exception handlers
+ superset/db_engine_specs/clickhouse.py:181:17: LOG014 `exc_info=` outside exception handlers
+ superset/db_engine_specs/hive.py:563:13: LOG014 `exc_info=` outside exception handlers
+ superset/sql_lab.py:138:69: LOG014 `exc_info=` outside exception handlers
+ superset/sql_lab.py:142:75: LOG014 `exc_info=` outside exception handlers
+ superset/tasks/cache.py:298:31: LOG014 `exc_info=` outside exception handlers
+ superset/utils/core.py:574:43: LOG014 `exc_info=` outside exception handlers
+ superset/views/error_handling.py:140:50: LOG014 `exc_info=` outside exception handlers
+ superset/views/error_handling.py:145:51: LOG014 `exc_info=` outside exception handlers
+ superset/views/error_handling.py:151:52: LOG014 `exc_info=` outside exception handlers
+ superset/views/error_handling.py:160:41: LOG014 `exc_info=` outside exception handlers
+ superset/views/error_handling.py:187:44: LOG014 `exc_info=` outside exception handlers
+ superset/views/error_handling.py:209:37: LOG014 `exc_info=` outside exception handlers

rotki/rotki (+0 -1 violations, +0 -0 fixes)

- rotkehlchen/api/server.py:439:29: RUF100 [*] Unused `noqa` directive (non-enabled: `LOG014`)

zulip/zulip (+1 -0 violations, +0 -0 fixes)

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

+ zerver/lib/push_notifications.py:1334:21: LOG014 `exc_info=` outside exception handlers

Changes by rule (2 rules affected)

code	total	+ violation	- violation	+ fix	- fix
LOG014	16	16	0	0	0
RUF100	1	0	1	0	0

Linter (preview)

✅ ecosystem check detected no linter changes.

[ntBre]

I'm kind of on the fence about the ecosystem results. Some of them seem like true positives, like the zulip case, but many of the others are in functions annotated with some kind of @app.exception_handler decorator. I'm not sure there's much we can do about this, though, as the type of app and the name of the decorator varies across packages. It might be rare enough that noqa is the answer, but I'm open to other thoughts here. In general it seems difficult to detect whether or not we're in an "exception handler," as the RUF100 case in rotki also demonstrates.

[ntBre]

I think stabilizing this is in line with other rules we've stabilized, and 16 ecosystem hits is not much overall. LOG004 and LOG014 are the only 2/7 LOG rules in preview still. I gave LOG004 a Stabilize* on Notion because of #18044, which I think we could help with a documentation fix and finish stabilizing the set.

[dylwil3]

I think it's okay to stabilize this for the reasons you give. Codebases with lots of custom exception handlers may choose not to enable the rule at all if it's noisy - it seems relatively niche to me.