Unused type angle brackets, and/or unnecessary angle brackets

What it does

It would be nice if clippy could detect whether such type notations are not necessary, and the code would compile without them:

fn test<T: Neg>(x: T) -> T {
    <T as Neg>::neg(x)
}

This would result in the following fixed code:

fn test<T: Neg>(x: T) -> T {
    T::neg(x)
}

However, the vision here is that this could also detect "partial refactoring" options like the below, which would also fix to the same output:

fn test<T: Neg>(x: T) -> T {
    <T>::neg(x)
}

Advantage

• Can help reduce code size and make code more understandable (for example, the resulting T::neg(x) could potentially be modified by other lints into x.neg() or -x in the case of operator methods).
• Can help make refactoring easier by letting the linter remove <> if you just search-and-replace as Trait> with >, rather than needing to use a regular expression.

Drawbacks

• The amount of type information needed for this is probably quite complicated, at least in the case of removing the as Trait portion.
• This is a pretty niche change that would probably require a lot of work.

Example

(your issue template is unable to determine that I already included examples)

Comparison with existing lints

Loads of "unnecessary X" lints exist in clippy, and so, this would fit right in.

Additional Context

No response

The issue names no files, tests, or entry points. Begin by studying Clippy's existing unnecessary-X lints and the type information needed for the Rust examples; done means detecting both forms of unnecessary angle brackets and providing the described fixed code.