Tracking remaining usage of the Ember global

With #19357 landing, there are a few deprecation notices being thrown even in brand new apps on 3.27-beta-1+.

Here’s a list:

• PR: https://github.com/embroider-build/embroider/pull/785 In compiled templates built with Embroider. const createTemplateFactory = Ember.HTMLBars.template;

• PR: https://github.com/embroider-build/embroider/pull/784 Before app boot, by ember-inflector from Ember Data Checks for Ember.ENV.EXTEND_PROTOTYPE in ember-inflector/make-configurable.js.

• PR: #19509 On didBecomeReady Object.keys is being called on the internal app context in findNamespaces, which includes the Ember “global”. tryIsNamespace then accesses the Ember object.

Steps to reproduce

Run ember new with ember-cli@3.27.0-beta.1. Inspect the console.

Relevant versions

ember-cli: 3.27.0-beta.1
ember-source: 3.27.0-beta.3
ember-data: 3.27.0-beta.0
ember-cli-htmlbars: 5.7.1
@embroider/compat: 0.39.1
@embroider/core: 0.39.1
@embroider/webpack: 0.39.1

[pzuraq]

@sandydoo the final issue should have been fixed by #19509, we removed the namespace processing entirely. That fix should be backported to beta in the next release.

[pzuraq]

I thought we tried to get rid of the Namespace stuff, I’m unsure why we had to keep it in the end. It’s odd that tests pass too, even with it. I’ll dig in soon.