chore: update minimum node version from 18.0 to 18.16

[LeoMcA]

Summary

Problem

some versions prior to 18.16 were causing ts-node to raise an error: RangeError: Maximum call stack size exceeded

Solution

bump minimum engine version in package.json

---

How did you test this change?

I've been using node 18.16 for months locally with no problems

[bsmth]

Confirming this version was needed to get builds running for me.

Previously (node 18.0.0)

$ ts-node tool/cli.ts optimize-client-build
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for /.../yari/tool/cli.ts
    at new NodeError (node:internal/errors:405:5)
    at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:99:9)
    at defaultGetFormat (node:internal/modules/esm/get_format:142:36)
    at defaultLoad (node:internal/modules/esm/load:91:20)
    at nextLoad (node:internal/modules/esm/hooks:733:28)
    at load (/.../yari/node_modules/ts-node/dist/child/child-loader.js:19:122)
    at nextLoad (node:internal/modules/esm/hooks:733:28)
    at Hooks.load (node:internal/modules/esm/hooks:377:26)
    at MessagePort.handleMessage (node:internal/modules/esm/worker:168:24)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:778:20) {
  code: 'ERR_UNKNOWN_FILE_EXTENSION'
}

with 18.16:

nvm use 18.16
# Now using node v18.16.1 (npm v9.5.1)
yarn && yarn dev
yarn install v1.22.19
[1/5] 🔍  Validating package.json...
...
$ ts-node tool/cli.ts optimize-client-build
(node:11694) ExperimentalWarning: Import assertions are not a stable feature of the JavaScript language. Avoid relying on their current behavior and syntax as those might change in a future version of Node.js.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:11694) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
info: Hashed 4 files in client/build/index.html