Module renaming needs to be opt-in

[amcasey]

In 3.1, we enabled renaming modules in imports (and exports?). So, for example, you can rename "file" in import { x } from "file".

I believe this was the key change: 24a5bdd

Older versions of VS will see that canRename is true in that location but fail to call getEditsForFileRename instead of findRenameLocations.

We probably need a UserPreference to make this behavior opt-in.

[amcasey]

The current behavior of VS is that the rename is allowed, but only updates the single location, introducing an error.

[minestarks]

Related issue #28679