no-internal-modules: configuration to opt in/out to enable/disable exports linting

Some time ago `no-internal-modules` rule added ES modules exports linting as a "fix" -> minor version bump (which was a breaking change btw).

From my experience, linting exports with this rule doesn't make much sense, as barrel/public-api files, can re-export from any nested path.
> for example angular public api patterns, nx patterns (with React as well)

**For better imagination I'm adding showcase of scaffold/public API**


**feature proposal**

- to mitigate these kind of discussions, I'd like to propose to add configuration API to this rule to opt out/in for linting exports

```
rules: {
'import/no-internal-modules': ['error',{lintExports:false}],
}
```

Start by locating the implementation and tests for the `no-internal-modules` rule, then inspect how its current ES module export linting is configured. The change is done when the rule supports the proposed `lintExports` option for opting in or out and tests cover both settings.

Written by the indexing model from the issue text.