Add catchSafeObjects option (default false) to no-get rule to catch get(foo, 'bar')

[bmish]

Previously, this rule could only catch instances with the this object in scenarios like get(this, ...) or getProperties(this, ...). But we can safely catch and autofix other objects besides this too:

Before:

import { get } from '@ember/object';
get(foo, 'bar');

After:

import { get } from '@ember/object';
foo.bar;

CC: @mongoose700

[rwjblue]

This change seems good to me, note: that this is both breaking and a bugfix. SemVer allows for such a thing, but its worth calling out in the changelog IMHO.

[bmish]

Planning to move this behind a new rule option...will update this PR.

[bmish]

Updated to move this behind a catchSafeObjects (default false) option that I will enable in the next major release.

I also plan to add another option catchUnsafeObjects (which will always default to false) for catching foo.get('bar') which likely involves an Ember Object but we can't be sure about it.

[rwjblue]

Gotcha, seems good to me. 😄

[bmish]

Follow-up PR to add catchUnsafeObjects option: #913