Ignore a case where Ember.get is distinct from get
Ignore a case where Ember.get is distinct from get

While we would prefer this to work, it is not a hard necessity, for (at
least) two reasons:

1. Use of `Ember.get` vs. the import from `@ember/object` is rare and
   should be discouraged.

2. Use of `get` is itself fairly unusual to *need* these days; most
   uses either will not hit this case, as in the deep key lookup (which
   is always just `unknown` anyways) or should be trivially replaced
   with direct property access (since Ember 3.1!).

emberjs/ember.js,emberjs/ember.js,emberjs/ember.js