Rename ruff_cli crate to ruff

[charliermarsh]

Summary

Long ago, we had a single ruff crate. We started to break that up, and at some point, we wanted to separate the CLI from the core library. So we created ruff_cli, which created a ruff binary. Later, the ruff crate was renamed to ruff_linter and further broken up into additional crates.

(This is all from memory -- I didn't bother to look through the history to ensure that this is 100% correct :))

Now that ruff no longer exists, this PR renames ruff_cli to ruff. The primary benefit is that the binary target and the crate name are now the same, which helps with downstream tooling like cargo-dist, and also removes some complexity from the crate and Cargo.toml itself.

Test Plan

• Ran rm -rf target/release.
• Ran cargo build --release.
• Verified that ./target/release/ruff was created.

[MichaReiser]

This will mess with my brain mussels...

[MichaReiser]

Is there anything that needs changing in the release workflow?

[github-actions]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

Formatter (stable)

✅ ecosystem check detected no format changes.

Formatter (preview)

✅ ecosystem check detected no format changes.

[charliermarsh]

@MichaReiser - I don't believe so because we build the binaries with Maturin (which works with the changes to pyproject.toml), and the binaries generated still have the same name.