Check all imports are via `using` (not `import`)

[nickrobinson251]

Would very much like this feature -- does it seem possible and a fit for this package?

i.e. convert

import Foo
import Bar: baz

to

using Foo: Foo
using Bar: Bar, baz

Users may need to change their code (if they previously extended baz like baz() = ... to do so like Bar.baz() = ...) so we'd have to tell them to do that in the text output i guess

(Perhaps we could even identify if any methods were extended this way? And list them? And choose between using Bar: Bar, baz and using Bar: baz appropriately?)

[ericphanson]

JuliaFormatter can do the toplevel conversion, but I don’t think it makes method definitions use the qualified name: https://domluna.github.io/JuliaFormatter.jl/dev/#import_to_using

We could probably do both but it would be a bit of a lift to be fully semantic rather than find and replace. Definitely lower priority than #114

[giordano]

I've been wanting to enforce no imports in the codebase I'm working on, so I'd like this feature as well!

[giordano]

I feel like I should start collecting the list of all cases I came across where import was actually harmful, last I found was CliMA/Oceananigans.jl#5262 (comment): you think you're extending a method from another module but you actually don't, and you only barely get an easy to miss warning. I'm really growing to hate import, it's quite problematic.