[FEAT] Add shouldParseScope, disableTemplateTag, disableFunctionCall options

[pzuraq]

This PR refactors modules to enable users to pass an options, with
three options currently supported:

1. shouldParseScope, which allows users to parse the scope parameter
   into a static format usable by the precompiler

   {
     modules: {
       'ember-cli-htmlbars': 'default',
       '@ember/template-compilation': {
         export: 'precompileTemplate',
         shouldParseScope: true,
       }
     }
   }

   When enabled, the scope parameter is parsed, and then turned into an
   array of the keys on the object. If a non-object is passed, or any of
   the keys or values are not references, then an error is thrown.

2. disableTemplateTag, which disables using the precompile macro as a
   template tag. This should be used for precompileTemplate in
   ember-cli-htmlbars

3. disableFunctionCall, which disables using the precompile macro as
   a function call. This should be used by experimental template import
   syntaxes.

This PR also refactors the way that imports statements are processed.
They're now parsed in the beginning, in Program, ensuring that the
parse step is only done once, and that we can build a list of all
present imports in the file. This allows us to support more than one
module at once.

[rwjblue]

Looks pretty good, thanks for working on it!

A few thoughts:

• I think adding the flexibility to disallowing one type of invocation or the other, but I don't really want to leverage it 😝
• Moving the ImportDeclaration hook to Program means that we can no longer detect imports that are created from other plugins (because Program will not be called again). This is already an issue with the Ember global import code we just landed (we'll have to fix this up in both babel plugins that have that code), we should be careful not to introduce even more of these race conditions.
• I think we should add @ember/template-compilation to the default values for the module. This is probably fine to add in a follow up PR though.

[rwjblue]

This seems vaguely odd, why do we reference first here? Can you update to either have the new modules format suggest a local name when the export is default (I think this option, but is pretty "legacy" IMO since we are generally going to use non-default exports going forward).

[rwjblue]

Chatted with @pzuraq about the import ordering issue, and going to fix that in a follow on.