Add destructuring support to new-modules-import rule

[clcuevas]

This PR updates the new-modules-import rule to account for destructuring assignments. Right now when enabling this rule, it will not report on Ember properties without the Ember.. Below is an example:

import Ember from 'ember';

// This does not get reported to ESLint
const { Component } = Ember;

export default Component.extend({ ... });

However...

import Ember from 'ember';

// This does get reported to ESLint
export default Ember.Component.extend({ ... });

I'd like to take advantage of this awesome rule and turn it on for the Ember applications I'm currently working on. However, all of my applications use destructuring assignments and the current rule's state does not send/report any ESLint errors like I'd like it to.

[caseywatts]

Thanks for working on this @clcuevas !
+1 do want :)

[Turbo87]

this could use a comment. what is this doing and why is it only relevant for the injections?

[rwjblue]

Looks pretty good to me. Can you add an invalid test for:

import Ember from 'ember';

const { 
  computed: {
    alias,
    uniq
  }
} = Ember;

[clcuevas]

@rwjblue @Turbo87 Your feedback has been addressed. Thanks!

[rwjblue]

Awesome, thank you!