Force absolute path for some items

What it does

Lint absolute_paths (#10568) warns about items that use an absolute path instead of a use.
Clippy misses the opposite lint: warn about unqualified paths that are imported where they should not.

Advantage

An example is the log crate, which is often used as log::info! or log::error!. Unfortunately, newcomers may be tempted to import the macros from the log crate.

For consistency, it would be good to have an option to enforce the use of the full path with clippy.

Drawbacks

No response

Example

use log::error;

fn f() {
    error!("fatal error in f");
}

Could be written as:

fn f() {
    log::error!("fatal error in f");
}

The issue names the existing absolute_paths lint (#10568) and shows the desired log::error! form. Start by reviewing that lint and the surrounding Clippy lint conventions; determine the supported scope for unqualified imports and how the option should behave. Done means the requested lint is implemented with coverage for the shown examples and documented behavior.