Unify Settings and AllSettings

[MichaReiser]

Summary

This PR merges AllSettings and Settings (by merging CliSettings into Settings). The main motivation is to avoid the confusion of why the two settings exist, which still isn't entirely clear to me.
Here's what I understand today (I am happy to close this PR if we can get to the bottom of why the two structs exist)

#1891 split Settings into AllSettings and Settings

We want to automatically derive Hash for the library settings, which
requires us to split off all the settings unused by the library
(since these shouldn't affect the hash used by ruff_cli::cache).

I solved this by extending the CacheKey derive macro to support the cache_key(ignore) field attribute to ignore individual fields. We can keep the automatically derived CacheKey implementation and explicitly mark the excluded fields.

There has been some argument whether the two settings exist because the CliSettings are only respected for the "root" configuration. This holds true for all CliSettings except cache-dir as #7520 showed. Meaning that distinction may have been true but no longer is.

My final guess is that the CliSettings used to be unique to using ruff from the cli. I think this is still mostly true (although most of the resolver code now lives inside ruff_workspace). However, I don't think it is sufficient reason to separate the two structs, especially considering that we could show diagnostics in our playground similar to biome (see console tab) where we would want to respect the output-format configuration (and --show-sources etc). fix, fix-only and cache-dir likely remain CLI only settings but, IMO, don't justify the cognitive load of having multiple settings structs.

The main justification for me to keep the separate settings struct is that the linter doesn't need the CliSettings. These are settings that only concern the diagnostic rendering, and file traversal (although the same is true for exclude, respect_gitignore and other global settings). That's why I plan to split settings in more semantic sub-settings:

• Linter settings
• Formatter settings
• common / shared settings
• Maybe; Resolver settings?

Test Plan

cargo test

[MichaReiser]

Current dependencies on/for this PR:

• main
  • PR Unify Settings and AllSettings #7532 👈
    • PR Extract ResolverSettings #7542
      • PR Introduce LinterSettings #7543
        • PR Move Settings and ResolverSettings to ruff_workspace #7544
          • PR Introduce FormatterSettings #7545
            • PR Create LintConfiguration #7548
              • PR Add lint section to Ruff configuration #7549
    • PR Rename ConfigProcessor to ConfigurationTransformer #7536

This comment was auto-generated by Graphite.

[github-actions]

PR Check Results

Ecosystem

✅ ecosystem check detected no changes.

[charliermarsh]

Nit: maybe a comment on why these are separated from the rest? Same with other instantiations.

[MichaReiser]

I'll leave it as is because these will be moved to their own struct in a PR higher in the stack, making the reason clear