False positive of `no-import-module-exports` on `module` variable defined in the module

```js
import 'something'; // => Cannot use import declarations in modules that export using CommonJS (module.exports = 'foo' or exports.bar = 'hi') import/no-import-module-exports

export const module = {};
module.foo = 42;
```

Start by reproducing the issue from the JavaScript example and trace the no-import-module-exports rule's handling of the locally defined module variable. Compare the diagnostic for this case with the rule's intended CommonJS module.exports or exports.bar cases. Done means the false positive is removed while genuine CommonJS export warnings remain covered.

Written by the indexing model from the issue text.