paragon [BD-46] [WIP] docs: upgrade gatsby to v5

Description

An attempt to upgrade gatsby to v5. Spoiler alert: everything breaks.

Deploy Preview

Include a direct link to your changes in this PR's deploy preview here (e.g., a specific component page).

Merge Checklist

[ ] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[ ] Does your change adhere to the documented style conventions?
[ ] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[ ] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[ ] Were your changes tested in the example app?
[ ] Is there adequate test coverage for your changes?
[ ] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

Nov 01 '23 07:11 viktorrusakov

Thanks for the pull request, @viktorrusakov!

This is currently a draft pull request. When it is ready for our review and all tests are green, click "Ready for Review", or remove "WIP" from the title, as appropriate.

Nov 01 '23 07:11 openedx-webhooks

Deploy Preview for paragon-openedx failed.

Name	Link
Latest commit	ac7ddbb06d1d1f56ad02027b12a5732f6ccae124
Latest deploy log	https://app.netlify.com/sites/paragon-openedx/deploys/6541ff7f5f1469000880dffe

Nov 01 '23 07:11 netlify[bot]

Problems

HEAP memory. The V8 engine has run out of memory (JavaScript heap), and it is unable to allocate more memory to the application or script. Removing the live editor, all pages except the main and component pages, and unnecessary plugins does not solve this problem. Changing the environment variable (NODE_OPTIONS=--max-old-space-size) to 8192 and 12288 still causes a memory limit error. Although on some devices (MacBook Pro, Apple M1 Pro chip, 16 GM memory) after a long assembly (3-5 minutes) it was possible to obtain an insignificant result, without functionality. To test performance, I removed all components and returned one component at a time to the project. The first problems of a long assembly begin to appear when 20 components are returned. If we return all 75 components, we return to the problem of using a large amount of memory.