chore(deps): update dependency @tsconfig/node16 to v16

[pleo-bot-renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@tsconfig/node16 (source)	^1.0.3 -> ^16.0.0
@tsconfig/node16 (source)	^1.0.4 -> ^16.0.0

---

Release Notes

tsconfig/bases (@​tsconfig/node16)

v16.1.3

Compare Source

v16.1.2

Compare Source

v16.1.1

Compare Source

v16.1.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "after 8am and before 4pm every weekday" in timezone CET, 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 these updates again.

---

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

---

This PR has been generated by Renovate Bot.

[pleo-bot-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: actions/pnpm-lock.yaml

 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

Your pnpm version is incompatible with "/tmp/renovate/base/repos/github/pleo-io/spa-tools/actions".

Expected version: 9.x
Got: 8.15.8

This is happening because the package's manifest has an engines.pnpm field specified.
To fix this issue, install the required pnpm version globally.

To install the latest version of pnpm, run "pnpm i -g pnpm".
To check your pnpm version, run "pnpm -v".

[DimitrisKaramanis]

This PR is going to be closed automatically, because it is created by a deprecated Renovate bot. A new PR will be created by the new renovate process, just sit back and relax. :)