feat: plugin install validation (#5261)

Validates the plugins provided through the initial config object.

If the plugin comes from an npm package check that the package has been
installed.

If the plugin is present further confirm that peer dependencies have
been installed. It then checks that the installed version falls within
the range of the originating package.

This leverages the node require mechanism based on `process.cwd()` as
the starting directory.

It supports peer dependencies installed not in the top level `node_modules`
but a sub-`node_modules` of the package of the plugin.

Resolves #5256

---------

Co-authored-by: Luis Schaab <[email protected]>

Author: kanej

pnpm-lock.yaml

@@ -53,6 +53,7 @@
     "@nomicfoundation/eslint-plugin-slow-imports": "workspace:^",
     "@reporters/github": "^1.7.0",
     "@types/node": "^20.0.0",
+    "@types/semver": "^7.5.8",
     "@typescript-eslint/eslint-plugin": "^7.7.1",
     "@typescript-eslint/parser": "^7.7.1",
     "c8": "^9.1.0",
@@ -73,6 +74,7 @@
   "dependencies": {
     "@nomicfoundation/hardhat-errors": "workspace:^3.0.0",
     "@nomicfoundation/hardhat-utils": "workspace:^3.0.0",
-    "chalk": "^5.3.0"
+    "chalk": "^5.3.0",
+    "semver": "^7.6.2"
   }
 }