Restore ember-try configuration for Ember Data

[backspace]

Thanks to @jlami for pointing out that I mistakenly deleted this.

I haven’t run the tests locally, I wouldn’t be surprised if this still needs some tweaking. We’ll see!

[backspace]

The blueprint has both ember-release and ember-default, maybe this is overkill for us 🤔

[broerse]

We will go with it for now. Thanks!

[jlami]

This looks much better! Thanks for your work @backspace

The only thing I can see is that the 'canary' scenario is failing in travis. Npm does not have a 'canary' tag for ember-data, so travis is failing on the npm install. Maybe we could use the bower way there? But https://github.com/components/ember-data is also in a confusing state and does not have a canary tag/branch as far as I can see. So maybe just use the beta there?

components/ember-data#38 (comment) seems to indicate that we could use the github master branch? But I always thought that github could not be used directly, since the publish step would generate the distribution packages. But maybe this is only for ember-source as ember-data is a 'normal' addon?

ember-default should be the one we have setup while developing, while the ember-release could easily change to 2.17 in the coming days. So I think it is good to have them both.