Build Memory Issues On CI Environments

[peterMuriuki]

Reference CI build e.g..

web: $ react-scripts build
web: Creating an optimized production build...
web: The build failed because the process exited too early. This probably means the system ran out of memory or someone called `kill -9` on the process.
web: error Command failed with exit code 1

Building the web app in CI environments intermittently fail with a 137 exit code which denotes that the running process ran out of memory and was killed.

The mitigation measures we have so far taken include:

1. Moving to use GHActions. This serves a 2-fold purpose. the first is because there is a preference in the company to use GHActions over other external CI platforms, and second, to avoid having to deal with paying for increased usage quotas on Circle CI.
2. Reducing the load on the CI environment by
   • Not generating source maps during the build
   • Reducing the concurrency levels when both building the packages using lerna, and running the tests.