[v2 backport] Pass owner instead of registry to ember-data's setupContainer

[anehx]

The setupContainer function of ember-data expects an application instance to be passed - in this case that is the faked owner object that we create when using a custom resolver in tests.

This behaviour previously worked because ember-data supported the usage of legacy function optionsForType which exists on the registry object. However, they removed that legacy fallback in v4 and replaced it with registerOptionsForType which does not exist on the registry but only on the owner.

Resolves #1386

[anehx]

@chriskrycho @MelSumner The tests for release, beta and canary will always fail here since this v2 of this addon still uses assign from @ember/polyfills which was removed in v5. However, I don't see the reason for the failing LTS tests.

Can someone support me with this? We currently can't update ember-data in various projects because of this issue, so this is important to us. Or is there already a release for v3 planned?