Update dependency nodemon to v3

This PR contains the following updates:

Package	Type	Update	Change
nodemon (source)	dependencies	major	`^2.0.14` -> `^3.0.0`

By merging this PR, the issue #43 will be automatically resolved and closed:

Severity	CVSS Score	CVE
Critical	9.8	CVE-2021-44906
Medium	5.3	CVE-2022-33987

By merging this PR, the issue #45 will be automatically resolved and closed:

Severity	CVSS Score	CVE
Medium	5.3	CVE-2022-25883

Release Notes

remy/nodemon (nodemon)

### [`v3.0.0`](https://redirect.github.com/remy/nodemon/releases/tag/v3.0.0) [Compare Source](https://redirect.github.com/remy/nodemon/compare/v2.0.22...v3.0.0) ##### Bug Fixes - also watch cjs ([86d5f40](https://redirect.github.com/remy/nodemon/commit/86d5f403a3e06e8aed48b37fa854730dc83257be)) - node@10 support back in ([af3b9e2](https://redirect.github.com/remy/nodemon/commit/af3b9e237281beffd92ceee0e2411ef53edcf375)) - semver vuln dep ([6bb8766](https://redirect.github.com/remy/nodemon/commit/6bb876666715e16464d48f98cd4bc2cba172a970)), closes [#2119](https://redirect.github.com/remy/nodemon/issues/2119) ##### Features - always use polling on IBM i ([3b58104](https://redirect.github.com/remy/nodemon/commit/3b5810463e7c39b0a8e2856c996faf454a6ca1f8)) ##### BREAKING CHANGES - official support for node@8 dropped. However there's no function being used in semver that breaks node 8, so it's technically still possible to run with node 8, but it will no longer be supported (or tested in CI). ### [`v2.0.22`](https://redirect.github.com/remy/nodemon/releases/tag/v2.0.22) [Compare Source](https://redirect.github.com/remy/nodemon/compare/v2.0.21...v2.0.22) ##### Bug Fixes - remove ts mapping if loader present ([f7816e4](https://redirect.github.com/remy/nodemon/commit/f7816e445b61e77dd57d5c9ccf5fa0be4f9b18a7)), closes [#2083](https://redirect.github.com/remy/nodemon/issues/2083) ### [`v2.0.21`](https://redirect.github.com/remy/nodemon/releases/tag/v2.0.21) [Compare Source](https://redirect.github.com/remy/nodemon/compare/v2.0.20...v2.0.21) ##### Bug Fixes - remove ts mapping if loader present ([1468397](https://redirect.github.com/remy/nodemon/commit/146839711be58995f88723b29de3007de87d6c3a)), closes [#2083](https://redirect.github.com/remy/nodemon/issues/2083) ### [`v2.0.20`](https://redirect.github.com/remy/nodemon/releases/tag/v2.0.20) [Compare Source](https://redirect.github.com/remy/nodemon/compare/v2.0.19...v2.0.20) ##### Bug Fixes - remove postinstall script ([e099e91](https://redirect.github.com/remy/nodemon/commit/e099e91cb6ff9cbb7912af86d22b91cd855a1ad0)) ### [`v2.0.19`](https://redirect.github.com/remy/nodemon/releases/tag/v2.0.19) [Compare Source](https://redirect.github.com/remy/nodemon/compare/v2.0.18...v2.0.19) ##### Bug Fixes - Replace update notifier with simplified deps ([#2033](https://redirect.github.com/remy/nodemon/issues/2033)) ([176c4a6](https://redirect.github.com/remy/nodemon/commit/176c4a6bed989fe94f103c905e5eee341d26794d)), closes [#1961](https://redirect.github.com/remy/nodemon/issues/1961) [#2028](https://redirect.github.com/remy/nodemon/issues/2028) ### [`v2.0.18`](https://redirect.github.com/remy/nodemon/releases/tag/v2.0.18) [Compare Source](https://redirect.github.com/remy/nodemon/compare/v2.0.17...v2.0.18) ##### Bug Fixes - revert update-notifier forcing esm ([1b3bc8c](https://redirect.github.com/remy/nodemon/commit/1b3bc8c3c839024d0de4392f56be571a4b660754)) ### [`v2.0.17`](https://redirect.github.com/remy/nodemon/releases/tag/v2.0.17) [Compare Source](https://redirect.github.com/remy/nodemon/compare/v2.0.16...v2.0.17) ##### Bug Fixes - bump update-notifier to v6.0.0 ([#2029](https://redirect.github.com/remy/nodemon/issues/2029)) ([0144e4f](https://redirect.github.com/remy/nodemon/commit/0144e4ff3e26ac7f8b3d1ee19fd9fd72f827780f)) - update packge-lock ([27e91c3](https://redirect.github.com/remy/nodemon/commit/27e91c36819d510a3e64111957a8ce13f0e186bc)) ### [`v2.0.16`](https://redirect.github.com/remy/nodemon/releases/tag/v2.0.16) [Compare Source](https://redirect.github.com/remy/nodemon/compare/v2.0.15...v2.0.16) ##### Bug Fixes - support windows by using path.delimiter ([e26aaa9](https://redirect.github.com/remy/nodemon/commit/e26aaa97d9ba245d33e82d42e248f72f50b1e351)) ### [`v2.0.15`](https://redirect.github.com/remy/nodemon/releases/tag/v2.0.15) [Compare Source](https://redirect.github.com/remy/nodemon/compare/v2.0.14...v2.0.15) ##### Bug Fixes - bump prod dep versions ([54784ab](https://redirect.github.com/remy/nodemon/commit/54784ab842a220777958cf590a49c5d9721f9834))

[ ] If you want to rebase/retry this PR, check this box

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: nodeJs/Graphql-Mutations/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: express-graphql@0.12.0
npm ERR! Found: graphql@16.2.0
npm ERR! node_modules/graphql
npm ERR!   graphql@"^16.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer graphql@"^14.7.0 || ^15.3.0" from express-graphql@0.12.0
npm ERR! node_modules/express-graphql
npm ERR!   express-graphql@"^0.12.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: graphql@15.9.0
npm ERR! node_modules/graphql
npm ERR!   peer graphql@"^14.7.0 || ^15.3.0" from express-graphql@0.12.0
npm ERR!   node_modules/express-graphql
npm ERR!     express-graphql@"^0.12.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-08-05T12_35_07_194Z-debug-0.log

File name: nodeJs/Graphql-Introspection/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: express-graphql@0.12.0
npm ERR! Found: graphql@16.2.0
npm ERR! node_modules/graphql
npm ERR!   graphql@"^16.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer graphql@"^14.7.0 || ^15.3.0" from express-graphql@0.12.0
npm ERR! node_modules/express-graphql
npm ERR!   express-graphql@"^0.12.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: graphql@15.9.0
npm ERR! node_modules/graphql
npm ERR!   peer graphql@"^14.7.0 || ^15.3.0" from express-graphql@0.12.0
npm ERR!   node_modules/express-graphql
npm ERR!     express-graphql@"^0.12.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-08-05T12_35_10_956Z-debug-0.log

File name: nodeJs/Graphql-Injection/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: express-graphql@0.12.0
npm ERR! Found: graphql@16.2.0
npm ERR! node_modules/graphql
npm ERR!   graphql@"^16.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer graphql@"^14.7.0 || ^15.3.0" from express-graphql@0.12.0
npm ERR! node_modules/express-graphql
npm ERR!   express-graphql@"^0.12.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: graphql@15.9.0
npm ERR! node_modules/graphql
npm ERR!   peer graphql@"^14.7.0 || ^15.3.0" from express-graphql@0.12.0
npm ERR!   node_modules/express-graphql
npm ERR!     express-graphql@"^0.12.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-08-05T12_35_14_090Z-debug-0.log

SharonKoch / skf-labs