Fix out-of-memory issues during webpack compile

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Our webpack compile process is teetering on the edge of node's default memory limits and it is causing problems.

1. Our webpack:assets:compile CI step is intermittently failing
2. We cannot build GitLab in memory-limited environments (e.g. Raspberry Pi)
3. Development environments are strained by increasing memory requirements

We need to take steps to alleviate this.

---

Original Description

I originally saw this during the CE->EE merge (https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/6068, https://gitlab.com/gitlab-org/gitlab-ee/-/jobs/73759600). After @timzallmann pushed a few commits, the spec passed and the CE->EE merge happened. However, master failed because https://gitlab.com/gitlab-org/gitlab-ee/pipelines/23563370 failed.

This issue is to track our efforts to solve this problem:

• https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/19590/diffs

/cc: @mikegreiling