build(npm): use specific overrides instead of legacy-peer-deps

allows us to handle these peer dependency
issues on a case by case basis, instead of
generally allowing it for all packages,
which could lead to unnoticed issues.

in this case the @mind-elixir/node-menu package
is still showing mind-elixir 2.x.x as peerDep,
which cannot be resolved, since we use v4

.npmrc

@@ -1,2 +1 @@
 save-prefix = ''
-legacy-peer-deps = true

package.json

@@ -211,5 +211,10 @@
     "webpack": "5.97.1",
     "webpack-cli": "6.0.1",
     "webpack-dev-middleware": "7.4.2"
+  },
+  "overrides": {
+    "@mind-elixir/node-menu": {
+      "mind-elixir": "$mind-elixir"
+    }
   }
 }