resolveAsset interface via new svg-jar service

[betocantu93]

In order to avoid locked in to a particular addon for resolving assets, let consumers choose how they resolve assets i.e. ember-cli-resolve-asset or ember-cli-ifa for the hbs strategy the host app must implement /services/svg-jar's resolveAsset method, this PR also guards FastBoot usage, honestly because I don't really understand how dynamic imports work in node and ember-cli-fastboot

Example using ember-cli-ifa

import EmberSvgJarService from 'ember-svg-jar/services/svg-jar';

export default class SvgJarService extends EmberSvgJarService {
  @service assetMap; //comes from ember-cli-ifa

 //interface 
  resolveAsset(path) {
    return this.assetMap.resolve(path);
  }
}

Example using ember-cli-resolve-asset

import EmberSvgJarService from 'ember-svg-jar/services/svg-jar';
import resolveAsset from 'ember-cli-resolve-asset';

export default class SvgJarService extends EmberSvgJarService {
 //interface 
  resolveAsset(path) {
    return resolveAsset(path);
  }
}

Example without any addon, this could potentially be the default one and avoid having to declare the service altogether

import EmberSvgJarService from 'ember-svg-jar/services/svg-jar';
import resolveAsset from 'ember-cli-resolve-asset';

export default class SvgJarService extends EmberSvgJarService {
 //interface 
  resolveAsset(path) {
     return path;
  }
}

[betocantu93]

maybe the guard vs fastboot broke embroider? 🤔

[betocantu93]

The ultimate intention of this PR is to give more flexibility and enable proper documentation of usage

[betocantu93]

Removed any dependency to resolves addons with this interface approach, I think this might be the best approach, and document how you could integrate any of these solutions...

[betocantu93]

I updated the ember-try for embroider scenarios, but I honestly don't think this PR should be stopped by the current state of embroider, what I mean is that hbs strategy does not currently work for embroider at all for a couple of reasons that I'd try to figure out from time to time, still here's the issue I opened at embroider: embroider-build/embroider#746

One way to get the tests green is to just literally remove the usage of hbs strategy for tests and/or somehow scope them behind a non-embroider scenarios

[jherdman]

This is going to take a little while to review.

[betocantu93]

@jherdman I can split this PR, leave all of the embroider part out of it, the important thing is the service and the interface, and we would need to state that this strategy currently doesn't work for embroider.

[jherdman]

Let's split this PR in two as you suggested. I'm not familiar with Embroider so it'll take a while to get up to speed on that aspect of this fix.