New lint: qualified `None` to help make code more readable

What it does

I'd like to suggest a new lint that checks for naked Nones and asks to qualify them with the inner type of the Option.

Advantage

• Code becomes more readable, especially when looked at without inlay hints.
• Might warn against unexpected type changes, that a naked None wouldn't catch.

Drawbacks

• This may not be for everyone, so I suggest "restricted" as the target lint group.

Example

fn myfunc(s: Option<String>) { .. }

myfunc(None);

Could be written as:

myfunc(None::<String>);

The lint should also ask to rewrite instances of Option::<T>::None as None::<T>.

Start from the issue's examples: naked None in an Option call should be qualified, and Option::::None should be rewritten as None::. Check how both forms should be diagnosed and tested, including the restricted lint group; done when the lint consistently identifies both cases and offers the requested rewrites.