Config flag to stop template from local resolution

[mixonic]

• Add disableLocalResolutionForTypes to the config, permits a type to block being locally resolved in a given collection.

edit: This summary is out of date. See #17 (comment)

[mixonic]

Adds two tests:

• glimmer-resolver/test/resolution-order-test.ts

  Line 69 in 90a4079

  test('Identifies `template` in `components` collection from `template:/app/routes/my-page`', function(assert) {

• glimmer-resolver/test/resolution-order-test.ts

  Line 148 in 90a4079

  test('Identifies `template` in `components` private collection from `template:/app/routes/my-page`', function(assert) {

[dgeb]

shouldn't we add types in the routes collection?

[mixonic]

yes thank you, adding this.

[mixonic]

Ok, the approach her has changed. Two semantic differences land here:

• First, if you resolve with only a type ('type', not 'type:name') then no resolution fallback steps will run. The type will be looked for only in namespace and collection of the referrer. This is useful for local lookup, and to force the collection of a global lookup (From Ember we call resolve('template', 'route:/app/routes/my-page') to force a template lookup in the routes collection).
• Second, local lookup will only occur for a type if the collection is that type's definitiveType. In Ember this ensures resolve('template:my-page', 'template:/app/routes/my-form') does not resolve a module at template:/app/routes/my-form/my-page.

[rwjblue]

This seems much better than the original flag. We should continue thinking of a better long term solution (or disambiguate better in Ember itself).

[mixonic]

One reason you might call this less than ideal is that resolve('template', 'route:/app/routes/my-page') implies you must have a second type (here route) in the routes collection in order to force lookup to a template in that collection. It might be better if resolve('template', ':/app/routes/my-page') without a type on the referrer was permitted.