debugging CI build failure

[jamigibbs]

Description

The original error said "no space left but I resolved this by adding the jlumbroso/free-disk-space@main action.

Error:ENOSPC: no space left on device, mkdir '/home/runner/work/veteran-facing-services-tools/veteran-facing-services-tools/packages/documentation/.cache/caches/gatsby-source-filesystem'

The next error I got during the Build step (yarn build) was:

Error:Failed to launch the browser process!
/home/runner/work/veteran-facing-services-tools/veteran-facing-services-tools/ packages/documentation/node_modules/puppeteer/.local-chromium/linux-722234/chrome-linux/chrome: error while loading shared libraries: libX11-xcb.so.1: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/master/docs/troubleshooting.md

I started to look into upgrading Gatsby because it's two major version behind.

When I updated to "gatsby": "^4.25.8",, locally I'm getting these incompatibility warnings which is probably why the build is not completing.

Testing done

Screenshots

Acceptance criteria

• [ ]

Definition of done

• Changes have been tested in vets-website
• Changes have been tested in IE11, if applicable
• Documentation has been updated, if applicable
• A link has been provided to the originating GitHub issue (or connected to it via ZenHub)
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs