Correct some #[clippy::version]s

[Alexendoo]

Some were a bit off

changelog: none

[rust-highfive]

r? @flip1995

(rust-highfive has picked a reviewer for you, use r? to override)

[flip1995]

How did you find those incorrect versions? Do you think that there could be a way to automatically check those?

I trust you on the new version numbers 👍

@bors r+

[bors]

📌 Commit 2b655d4 has been approved by flip1995

[bors]

⌛ Testing commit 2b655d4 with merge 65f518e...

[xFrednet]

I think this issue would be solved by having nightly lint's and then set the version on a sync, when we enable/release new lints.

I still have the nightly lint Implementation in my backlog, but I'm held up on some implementation details. Until then it would be cool, to detect this somehow 👍

[Alexendoo]

I did it using a rather hacky script that installed a bunch of stable toolchains and checked for the lint names in the output of clippy-driver -W help

Detecting it automatically would be nice, maybe metadata collector could parse the changelog New Lints sections in the meanwhile

[bors]

☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test
Approved by: flip1995
Pushing 65f518e to master...

[flip1995]

The way I would go about it is checking out the gh-pages branch and write a script tracking when a new lint impl was added and comparing it with the version in the documentation.

But yeah, once we have nightly lints, and a stabilization procedure for those in place, automating it will be way easier.