Remove the import/no-internal-modules lint rule

With Node.js adopting a standard for packages to declare their exports,
this rule may not be useful anymore. It should be legal to import any
valid export from a package.

An open [issue] on eslint-plugin-import tracks this ecosystem feature
and when that resolves there may be a better rule to enable.

[issue]: import-js/eslint-plugin-import#1868

Author: tilgovi

.eslintrc.js

@@ -18,7 +18,6 @@
  * under the License.
  */
 
-const path = require('path');
 const babel = require('@babel/core');
 
 // Use the root babel.config.js for module resolution.
@@ -44,7 +43,6 @@ module.exports = {
     'import/newline-after-import': 'error',
     'import/no-absolute-path': 'error',
     'import/no-default-export': 'error',
-    'import/no-internal-modules': 'error',
     'import/order': [
       'error',
       {
@@ -141,12 +139,6 @@ module.exports = {
         assert: true,
       },
       rules: {
-        'import/no-internal-modules': [
-          'error',
-          {
-            allow: [path.resolve(__dirname, './packages/*/src/**')],
-          },
-        ],
         'import/no-relative-parent-imports': 'off',
       },
     },