build(yarn): reset script now wipes node modules, yarn lock

Found myself in need of this when strange errors started occurring
between branch switches where the gRPC tooling was not installed
properly despite the configure script running successfully.
Now the reset is script is much more robust and it closer
resembles the outcome of a fresh clone.

Also: Ran the reset script and it updated the lock file, including
that in the commit as well to see if in the future othe reset runs
will also generate these/similar changes to the lock file or not.

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>

package.json

@@ -14,7 +14,10 @@
   },
   "scripts": {
     "run-ci": "./tools/ci.sh",
-    "reset": "git clean -f -X && yarn run configure",
+    "reset:node-modules": "del-cli --dry-run '**/node_modules'",
+    "reset:git": "git clean -f -X",
+    "reset:yarn-lock": "del-cli yarn.lock && yarn install --update-checksums --force",
+    "reset": "run-s reset:git reset:node-modules reset:yarn-lock configure",
     "configure": "yarn install --frozen-lockfile --non-interactive && yarn run build:dev:backend",
     "install-yarn": "npm install --global yarn@1.19.0",
     "custom-checks": "TS_NODE_PROJECT=./tools/tsconfig.json node --trace-deprecation --experimental-modules --abort-on-uncaught-exception --loader ts-node/esm --experimental-specifier-resolution=node ./tools/custom-checks/run-custom-checks.ts",