Introduce resolver option to test module

[trentmwillis]

Addresses #173. After implementing, I realize this could potentially break some one that has already been using the resolver property in their passed in environment, but I think that risk is acceptable.

[rwjblue]

Seems like this should be changed in test-module.js (moduleFor also supports integration: true so it needs/uses a resolver) around here. Once that is changed, I'm not sure that the test-module-for-integration.js or test-module-for-component need to be changed as much...

[trentmwillis]

@rwjblue test-module.js is changed. test-module-for-component inherits from test-module, so that is fine. Then test-module-for-integration inherits directly from abstract-test-module, so it also needs the changes.

Also, looks like Canary and Alpha are failing, for ambiguous reasons.

[rwjblue]

Yeah, I keep fighting with canary + alpha on CI. I'll look at that separately.

[trentmwillis]

Seems like we could just make Canary an allowed failure. Also, could we drop some of the versions we test against and split the tests up into different processes?

[rwjblue]

Looks like canary was passing in #175, maybe try rebasing?

[trentmwillis]

@rwjblue rebased and all is green now

[rwjblue]

Released in v0.5.33.