fix(deps): update dependency @types/node to v18

[bcgov-devops]

This PR contains the following updates:

Package	Type	Update	Change	Pending
@types/node (source)	dependencies	major	^16.18.25 -> ^18.0.0	18.17.9 (+3)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Renovate Bot.

---

Thanks for the PR!

Any successful deployments (not always required) will be available below.
Frontend available

Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

---

Thanks for the PR!

Any successful deployments (not always required) will be available below.
Frontend

Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

[bcgov-devops]

⚠ 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: frontend/package-lock.json

[DerekRoberts]

This can't be updated before node itself. Closing.

[bcgov-devops]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 18.x releases. But if you manually upgrade to 18.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

[DerekRoberts]

Correction. Our builder is using Node 20. This dependency update brings us closer to lining up versions.