chore(deps): update dependency nodemon to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
nodemon (source)	2.0.22 -> 3.1.9

---

Release Notes

remy/nodemon (nodemon)

v3.1.9

Compare Source

Bug Fixes

• maintain backward support for exitcrash (9c9de6e)

v3.1.8

Compare Source

Bug Fixes

• types updated (cb91187)

v3.1.7

Compare Source

v3.1.6

Compare Source

Bug Fixes

• watch nested paths (11fcaaa), closes #​2216

v3.1.5

Compare Source

v3.1.4

Compare Source

v3.1.3

Compare Source

Bug Fixes

• cast the nodemon function as Nodemon type (eaa1d54), closes #​2206

v3.1.2

Compare Source

v3.1.1

Compare Source

Bug Fixes

• add types to help with required nodemon usage (#​2204) (cd27c0b)

v3.1.0

Compare Source

Features

• Enable nodemon to monitor file removal (#​2182) (02d216f)

v3.0.3

Compare Source

Bug Fixes

• use node when using --import (d3ee86e), closes #​2157

v3.0.2

Compare Source

Bug Fixes

• bump debug out of vuln range (533ad9c), closes #​2146

v3.0.1

Compare Source

Bug Fixes

• restore default ext watch behaviour (95bee00), closes #​2124 #​1957

v3.0.0

Compare Source

Bug Fixes

• also watch cjs (86d5f40)
• node@10 support back in (af3b9e2)
• semver vuln dep (6bb8766), closes #​2119

Features

• always use polling on IBM i (3b58104)

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).

---

Configuration

📅 Schedule: Branch creation - "after 4am and before 7am on saturday" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact 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: package-lock.json

ERROR: npm v10.4.0 is known not to run on Node.js v14.21.3.  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/opt/containerbase/tools/npm/10.4.0/node_modules/npm/node_modules/@npmcli/agent/lib/agents.js:105
    options.lookup ??= this.#options.lookup
                   ^^^

SyntaxError: Unexpected token '??='
    at wrapSafe (internal/modules/cjs/loader.js:1029:16)
    at Module._compile (internal/modules/cjs/loader.js:1078:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)
    at Module.load (internal/modules/cjs/loader.js:979:32)
    at Function.Module._load (internal/modules/cjs/loader.js:819:12)
    at Module.require (internal/modules/cjs/loader.js:1003:19)
    at require (internal/modules/cjs/helpers.js:107:18)
    at Object.<anonymous> (/opt/containerbase/tools/npm/10.4.0/node_modules/npm/node_modules/@npmcli/agent/lib/index.js:7:15)
    at Module._compile (internal/modules/cjs/loader.js:1114:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact 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: package-lock.json

ERROR: npm v10.9.2 is known not to run on Node.js v14.21.3.  This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.

ERROR:
/opt/containerbase/tools/npm/10.9.2/14.21.3/node_modules/npm/lib/utils/error-message.js:11
  er.message &&= replaceInfo(er.message)
             ^^^

SyntaxError: Unexpected token '&&='
    at wrapSafe (internal/modules/cjs/loader.js:1029:16)
    at Module._compile (internal/modules/cjs/loader.js:1078:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)
    at Module.load (internal/modules/cjs/loader.js:979:32)
    at Function.Module._load (internal/modules/cjs/loader.js:819:12)
    at Module.require (internal/modules/cjs/loader.js:1003:19)
    at require (internal/modules/cjs/helpers.js:107:18)
    at Object.<anonymous> (/opt/containerbase/tools/npm/10.9.2/14.21.3/node_modules/npm/lib/cli/exit-handler.js:2:48)
    at Module._compile (internal/modules/cjs/loader.js:1114:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)