chore: Update .gitpod to use correct Node version

[markacola]

Description

Update Gitpod to use node version 18.

Added commands according to Gitpod documentation, except updated bash var to NODE_VERSION instead of the more generic VERSION suggested.

Documentation

N/A - this just allows the current gitpod config to run correctly.

Related Issues

N/A - I haven't created any separate issues for this.

Currently, opening the repo in Gitpod, or locally as a container in VSCode, yields the following error:

yarn run v1.21.0
error @: The engine "node" is incompatible with this module. Expected version ">=18.0.0". Got "16.13.0"
error Commands cannot run with an incompatible environment.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this **command.**

[LekoArts]

Hi, thanks for the PR!

The repository already contains a .nvmrc file so in theory the script could just call nvm use, correct?

[markacola]

Unfortunately, without the explicit installation, that results in:

Found '/workspaces/gatsby/.nvmrc' with version <18>
N/A: version "18 -> N/A" is not yet installed.

You need to run "nvm install 18" to install it before using it.

I will update the Dockerfile to bring in the .nvmrc file when building the image, update the command to just nvm install, and update to nvm use at runtime.

I've confirmed this is working as expected locally using the VSCode Devcontainer feature.
Would it be worth including the generated .devcontainer/devcontainer.json config file as well for other VSCode contributors?

{
  "name": "Existing Dockerfile",
  "build": {
    "context": "..",
    "dockerfile": "../.gitpod.Dockerfile"
  }
}

[LekoArts]

PR as-is looks good to me.

I think the dev container thingy is a separate discussion. From my testing with GitHub codespaces the repository just worked, it didn't have the niceties installed like the gitpod version though.

I'm open for adding a devcontainer config (https://docs.github.com/en/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces) but let's do that in another PR :)