Update Node.js version to match Cloudflare v3 build system default runtime

[brianzelip]

This PR updates the Node.js version to match the default Node runtime used by the latest Cloudflare v3 build system. The site was set to use the v3 system via the Cloudflare dashboard just before this PR.

[crugas]

Approved. Just out of curiosity, is there a way to determine how updating dependency versions affect the website? I'm thinking of a scenario where an updated dependency introduces unexpected behavior to the site. Perhaps a test space for techdocs for major dependency updates?

[cloudflare-workers-and-pages]

Deploying archivesspace-tech-docs with    Cloudflare Pages

Latest commit:	3b525d5
Status:	✅  Deploy successful!
Preview URL:	https://ba5daaee.archivesspace-tech-docs.pages.dev
Branch Preview URL:	https://update-node-version-to-match.archivesspace-tech-docs.pages.dev

View logs

[brianzelip]

@crugas yes there are a couple ways. This PR environment itself tests it...that's what CI is for. See the "All checks have passed" section herein. The "Cloudflare Pages" check shows a status of "Deployed successfully". That is one such that checks whether or not deployment breaks with the proposed changes.

Testing locally is another way, etc.

[crugas]

@crugas yes there are a couple ways. This PR environment itself tests it...that's what CI is for. See the "All checks have passed" section herein. The "Cloudflare Pages" check shows a status of "Deployed successfully". That is one such that checks whether or not deployment breaks with the proposed changes.

Testing locally is another way, etc.

Ah cool! I wasn't sure what the tests were testing for, so it's good to know that the Cloudfare Pages test deploys a dev version with the updated dependency and sees if it's breaking or not. I take it users could also go clicking around on that dev site (https://update-node-version-to-match.archivesspace-tech-docs.pages.dev/) if they really wanted to test things out themselves too. Thanks!