Deprecate configuring ember-cli-memory-leak-detector via config/environment.js

[bertdeblock]

Since all the work happens at build time, we can ask the user to define the configuration in ember-cli-build.js instead. This also prevents the configuration from being added to the app's meta tag even when ember-cli-memory-leak-detector is disabled.

Closes #39.

[bertdeblock]

@steveszc Any pointers on getting CI to pass? I could be wrong, but it seems that the test apps are using a published version of ember-cli-memory-leak-detector during CI? If that's the case, then I'm not sure how I can make CI pass here.

[steveszc]

@bertdeblock oh nice catch, I think you are probably right. Feel free to push another commit to this branch that uses '*' as the version number for ember-cli-memory-leak-detector dependency in the test packages. I think that is probably the right approach here... we could also update the version number in the test packages, but that could easily get out of date again.

[bertdeblock]

Okay, updated those versions and now (hopefully) CI should pass. I've noticed that running the test suite locally sometimes fails and sometimes it doesn't, even for the main branch. Unclear to me as to why this happens.

[bertdeblock]

@steveszc Mind approving the workflow?

[steveszc]

@bertdeblock Looks like we're green, I'll approve and merge. I also noticed the flakiness of the test suite recently. Not sure exactly what is going on there but definitely something I need to look in to. It may be related to the Qunit issues that have been reported #49

[steveszc]

Thanks for the contribution @bertdeblock!
Fixes #39

[bertdeblock]

Thank you @steveszc!