Remove deprecated extend-ignore and extend-unfixable options

[MichaReiser]

Summary

This PR removes the deprecated lint.extend-ignore and lint.extend-unfixable options. The options were deprecated in #2312 (0.0.238)

Part of #7650

Test Plan

Running ruff with a configuration containing extend-ignore or extend-unfixable now fails

❯ ../ruff/target/debug/ruff check test.py --no-cache
ruff failed
  Cause: Failed to parse /home/micha/astral/test/pyproject.toml
  Cause: TOML parse error at line 38, column 1
   |
38 | [tool.ruff.lint]
   | ^^^^^^^^^^^^^^^^
unknown field `extend-ignore`

Changing the option to ignore "ignores" the rule as expected.

[MichaReiser]

This is a bit unfortunate. We never added deprecation warnings to the CLI. I'm inclined to keep and hide the CLI options for now but add a deprecation warning instead.

It also seems that python-lsp-ruff is using the CLI option :(

https://github.com/python-lsp/python-lsp-ruff/blob/34acd6ed6daaaa3f2756a1a1cf1bfc2d76df7d0f/pylsp_ruff/plugin.py#L611-L612

[charliermarsh]

Yeah, I would vote not to remove these. They were never properly deprecated. Honestly, I would vote not to deprecate them, even (or to un-deprecate them). I think it would be surprising to users that they don't exist. If they didn't exist, I would consider adding them, even though they're undifferentiated from ignore and unfixable.

[github-actions]

ruff-ecosystem results

Linter (stable)

ℹ️ ecosystem check encountered linter errors. (no lint changes; 4 project errors)

latchbio/latch (error)

ruff failed
  Cause: Failed to parse /home/runner/work/ruff/ruff/checkouts/latchbio:latch/pyproject.toml
  Cause: TOML parse error at line 18, column 1
   |
18 | [tool.ruff]
   | ^^^^^^^^^^^
unknown field `extend-ignore`

python-trio/trio (error)

ruff failed
  Cause: Failed to parse /home/runner/work/ruff/ruff/checkouts/python-trio:trio/pyproject.toml
  Cause: TOML parse error at line 102, column 1
    |
102 | [tool.ruff.lint]
    | ^^^^^^^^^^^^^^^^
unknown field `extend-ignore`

mesonbuild/meson-python (error)

ruff failed
  Cause: Failed to parse /home/runner/work/ruff/ruff/checkouts/mesonbuild:meson-python/pyproject.toml
  Cause: TOML parse error at line 80, column 1
   |
80 | [tool.ruff]
   | ^^^^^^^^^^^
unknown field `extend-ignore`

pdm-project/pdm (error)

ruff failed
  Cause: Failed to parse /home/runner/work/ruff/ruff/checkouts/pdm-project:pdm/pyproject.toml
  Cause: TOML parse error at line 169, column 1
    |
169 | [tool.ruff.lint]
    | ^^^^^^^^^^^^^^^^
unknown field `extend-ignore`

Linter (preview)

ℹ️ ecosystem check encountered linter errors. (no lint changes; 4 project errors)

latchbio/latch (error)

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

ruff failed
  Cause: Failed to parse /home/runner/work/ruff/ruff/checkouts/latchbio:latch/pyproject.toml
  Cause: TOML parse error at line 18, column 1
   |
18 | [tool.ruff]
   | ^^^^^^^^^^^
unknown field `extend-ignore`

python-trio/trio (error)

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

ruff failed
  Cause: Failed to parse /home/runner/work/ruff/ruff/checkouts/python-trio:trio/pyproject.toml
  Cause: TOML parse error at line 102, column 1
    |
102 | [tool.ruff.lint]
    | ^^^^^^^^^^^^^^^^
unknown field `extend-ignore`

mesonbuild/meson-python (error)

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

ruff failed
  Cause: Failed to parse /home/runner/work/ruff/ruff/checkouts/mesonbuild:meson-python/pyproject.toml
  Cause: TOML parse error at line 80, column 1
   |
80 | [tool.ruff]
   | ^^^^^^^^^^^
unknown field `extend-ignore`

pdm-project/pdm (error)

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

ruff failed
  Cause: Failed to parse /home/runner/work/ruff/ruff/checkouts/pdm-project:pdm/pyproject.toml
  Cause: TOML parse error at line 169, column 1
    |
169 | [tool.ruff.lint]
    | ^^^^^^^^^^^^^^^^
unknown field `extend-ignore`

[MichaReiser]

I'll create an issue to follow up on this. Closing as per @charliermarsh's comment.

Follow up in #12014