How do we expect tools to handle import shorthands?

@bwilkerson raised some concerns about the tooling experience for import shorthands. If we implement this proposal, there will now be essentially four (or more) different ways to write an import/export.

How do we expect tools to deal with this? Will we be deprecating the old syntax? Presumably not, since it is more general. If not, is this a configuration knob? "Add imports using ...."? Or do the tools try to guess based on existing uses? What if it's invalid to use the predominant syntax?

In general, are there usability issues we need to consider here?

cc @lrhn @munificent @eernstg @natebosch @jakemac53 @bwilkerson

Start with the discussion in issue #1940 and review the import-shorthand proposal it references. Identify the expected behavior for tools, including syntax compatibility, deprecation, configuration, and existing-code detection. Done means the usability questions have a documented, agreed resolution.

Written by the indexing model from the issue text.