chore: add clippy rules for codebase consistency

[syjn99]

What was wrong?

Our PR reviews often contain this kind of comment, let Clippy handle it.

How was it fixed?

• Use clippy lints and lint configurations.
• Add cargo-workspace-lints on current CI.

Rationale

• let_and_return (Link): Few cases for assigning variables before returning.
• uninlined_format_args (Link): Inline arguments as possible as we can. Note that this rule couldn't detect macros from tracing.
• unnecessary_debug_formatting (Link): Use path.display() for printing the file path.
• unwrap_used (Link): Stop using unwrap() for production code, use expect() instead.
• useless_let_if_seq (Link): I think this style is better :)
• wildcard_imports (Link): This rule reminds me of this comment, which is reasonable.

Side note

I guess needless_pass_by_value (Link) can be helpful and is often a topic for our PR comments, but this leads so many LOC to satisfy the linter. I'd like the team to share opinions on it.

To-Do

• I have read CONTRIBUTING.md.
• This PR title follows conventional commits.

[KolbyML]

Can you add a CI to ensure we don't forget to add lints.workspace = true in the future, we should be able to use this https://crates.io/crates/cargo-workspace-lints ?

[syjn99]

Converting to draft as I'm adding more rules.

[jihoonsong]

This is very nice. This doesn't have to be perfect imo. Once this change is in place, if it feels like over 80 out of 100 to us, that’s good; if it feels over 90, that’s awesome.

[KolbyML]

looks good, we should use needless_pass_by_value

[KolbyML]

actually there is a few cases were it wouldn't make sense and I am not sure if the linter is able to pick that up or not so, never mind