new lint: catch creation of Strings from literals where literal/str would do

Let's say we have a function/struct with an argument/field like this:

fn print<T: AsRef<str> + std::fmt::Display>(string: T) {
...
}

When passing literals into it, one could do something like
print(String::from("hello world")); or
print(&String::from("hello world")); or
print(&"hello world");
or even print(&format!("hello world")) // will trigger useless_format but these conversions seem unnecessary because a cheap simple print("hello world"); will do.

Start by reviewing Clippy's existing useless_format lint and the examples in the issue. Determine which literal-to-String constructions should be diagnosed when a literal can be passed directly, then verify the lint covers the listed String::from, borrowed String, and borrowed literal cases without overlapping the existing lint.