Conflicts in `#[macro_use] extern crate` imports are treated in ad hoc way

Currently, if the some name is imported by macro_use for the second time it overwrites the previous import with the same name, so the last name "wins".
(At least when the second macro_use comes from a macro such overwriting is reported as an error.)

Also there's no distinction between explicit macro_use(name) with arguments and "glob" macro_use without arguments, and a "glob" can overwrite an explicit import.

Typically, name resolution in rust doesn't behave this way.
Typically it is order-independent, explicit names shadow glob names, and glob ambiguities are reported as errors on use.

In practice, we should be able to adjust the rules for #[macro_use] extern crates to follow the usual name resolution practices without much breakage.

This is an issue to link from https://github.com/rust-lang/reference/pull/2057.

Start by investigating Rust name resolution for #[macro_use] extern crate imports, including explicit macro_use(name) and glob macro_use forms. Define the desired order-independent behavior, explicit-over-glob precedence, and treatment of glob ambiguities; done means the rules are specified and validated without the current ad hoc overwriting.