chore: separate Cargo lint configuration

Keep the workspace lint configuration in its own Cargo metadata table
instead of letting it follow the dependency table directly. This makes the
manifest layout explicit for future dependency additions and keeps lint policy
visibly separate from package dependencies.

There is no runtime behavior change. Users should see the same binary behavior,
while maintainers get a clearer manifest structure.

Test Plan:
- cargo clippy
- cargo clippy --benches
- cargo clippy --tests
- cargo +nightly fmt
- cargo clippy
- cargo clippy --benches
- cargo clippy --tests

Refs: none

Cargo.toml

@@ -5,6 +5,7 @@ edition = "2024"
 
 [dependencies]
 
+[lints]
 [lints.rust]
 unsafe_code = "forbid"