chore: small adjustments

[tcoratger]

Description

@Pratyush Here I propose a slightly different formalism to manage lints compared to what we had before on the repo. This formalism inherits from what is already done on reth https://github.com/paradigmxyz/reth/blob/83af493179393c81dc2c48374306f2b88cc075db/Cargo.toml#L160-L254 with a curated list of lints that have already proven themselves.

In this methodology, lints are directly introduced into the cargo.toml file and then dispatched to all the crates inside the repo via

[lints]
workspace = true

So it's easier to manage and more uniform. For now I have only applied it to the poly crate but we can adopt this for the other crates in follow up PRs if you agree.

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against correct branch (master)
• Linked to GitHub issue with discussion and accepted design OR have an explanation in the PR that describes this work.
• Wrote unit tests
• Updated relevant documentation in the code
• Added a relevant changelog entry to the Pending section in CHANGELOG.md
• Re-reviewed Files changed in the GitHub PR explorer

[Pratyush]

Thanks for the PR, this is great! If you could propagate this to the other crates in the repo as well that would be lovely =). We should also add it to the template https://github.com/arkworks-rs/template so that future repos will inherit it

[tcoratger]

Thanks for the PR, this is great! If you could propagate this to the other crates in the repo as well that would be lovely =). We should also add it to the template https://github.com/arkworks-rs/template so that future repos will inherit it

@Pratyush Yes no problem, will propagate this in follow up PRs, one for each crate so that we have an easier review each time :)