[BUGFIX] Canary FEATURES flagging shouldn't produce warnings in canary

[jayphelps]

See discussion below.
Fixes #9309 (comment)

Cc/ @rwjblue, @igorT

[igorT]

re: my comment I am running a canary build and still see the isEnabled warning

[jayphelps]

@igorT ...shit shit... Okiedoke. Gimmie a bit.

[jayphelps]

@rwjblue ahh. so the issue is https://github.com/emberjs/ember.js/pull/9309/files#diff-f5a9575f74b90dcc366c4a161d779d16R196 is stripped, even in canary builds because duh, I didn't set it in the features.json. I don't really think it belongs in there, so I assume the only other place would be in the Brocfile...which is still hacky but that's the best I've got if we use this method of detection. Looking at the code more, I can't figure out how this could be done without maintaining a change to the master Brocfile but never merging it into the other branches.

Gonna have to defer to Robert on the best course of action since he knows the build process far better than anyone..

[rwjblue]

@jayphelps - Add it to features.json with a null value. All null features are set to false as part of the canary to beta branching process.

[jayphelps]

@rwjblue Done. lmk.

[rwjblue]

LGTM, thanks!