Remove output format text and use format full by default

[MichaReiser]

Summary

This PR removes support for the output format text in favor of concise and makes full the new default (it was already the default for preview mode). The OutputFormat::Text is still defined in code so that we can error when it's being used.

Resolves #7349

Test Plan

I tested that using --output-format on the CLI errors:

❯ cargo run --bin ruff -- check --output-format text
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.12s
     Running `target/debug/ruff check --output-format text`
ruff failed
  Cause: `--output-format=text` is deprecated. Use `--output-format=full` or `--output-format=concise` instead.

❯ cargo run --bin ruff -- check --config="output-format='text'"
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.12s
     Running `target/debug/ruff check '--config=output-format='\''text'\'''`
ruff failed
  Cause: The Setting `output_format=text` has been deprecated. Update your `--config` CLI arguments to use `output-format="concise"` or  `output-format="full"` instead.

I verified that using output-format="text" in the settings errors

❯ ../ruff/target/debug/ruff check test.py
ruff failed
  Cause: The Setting `output_format=text` has been deprecated. Update `pyproject.toml` to use `output-format="concise"` or  `output-format="full"` instead.

• I verified that using concise in the settings or on the CLI works as expected
• I verified that ruff defaults to full when no output-format is specified on the CLI or in the settings.

[MichaReiser]

This looks like a bug but it isn't. Or, it is a bug in the test rule that always emits an empty range instead of emitting an actual range.

[github-actions]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

[zanieb]

I'm a little worried about making this change when the full format is half-complete (#7352)

[MichaReiser]

@zanieb what's the part that you're worried about?

I think showing the code frame for diagnostics is already an improvement by itself worth shipping and the format name full is generic enough to allow us to also show fixes in a future version.

[zanieb]

It just doesn't feel as useful over the concise output without the fixes being shown (seen feedback from one user about this). Oh well though.

[MichaReiser]

I personally find the source text in the rust compiler extremely useful. I don't think I ever look at the line number to get context on where I need to fix something.

[snowsignal]

LGTM - it might be nice to have a small test plan :)

[MichaReiser]

I updated the PR to keep the Text option for now but I made the usage of Text a hard error.