Update eslint-plugin-import

2.28.0 introduced a breaking change to `import/order` where the order
of nested groups (whose purpose is to define different types of imports
that are of equivalent rank) started to matter: a single nested group
would be treated as though it wasn't nested

We [got around this][1] by adding a second nested group with most if
not all of the other import types we use

It looks like #141
brought us back to 2.27.5. If we go back to 2.28.0 now and revert to
the simpler config, for some reason the ESLint errors don't reappear

In any case, I submitted a [bug fix][2] in eslint-plugin-import 💅
This was released in 2.28.1, so we should upgrade, hopefully preventing
an unexpected return to confusing errors

[1]: ab5a73e
[2]: import-js/eslint-plugin-import#2854

Author: yndajas

.eslintrc.json

@@ -105,10 +105,7 @@
       "error",
       {
         "alphabetize": { "order": "asc", "orderImportKind": "asc" },
-        "groups": [
-          ["builtin", "external"],
-          ["internal", "parent", "sibling"]
-        ],
+        "groups": [["builtin", "external"]],
         "newlines-between": "always"
       }
     ],

package-lock.json

@@ -121,7 +121,7 @@
     "eslint-config-prettier": "^9.0.0",
     "eslint-import-resolver-typescript": "^3.5.5",
     "eslint-plugin-cypress": "^2.13.2",
-    "eslint-plugin-import": "^2.27.5",
+    "eslint-plugin-import": "^2.28.1",
     "eslint-plugin-no-only-tests": "^3.1.0",
     "eslint-plugin-prettier": "^5.0.0",
     "eslint-plugin-sort-exports": "^0.8.0",