[Chore] - Updated CI and Added Caching Feature

[adithyaakrishna]

Description:

• Updated CodeQL Workflow
• Enabled Caching for Workflows
• We won't be caching node_modules as according to https://github.com/actions/cache/blob/main/examples.md#node---npm, it is not recommended

Instead of using npm install we would be using npm ci which is usually used for CI Environments

[codecov]

Codecov Report

Merging #691 (b533005) into master (69f3144) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #691   +/-   ##
=======================================
  Coverage   83.06%   83.07%           
=======================================
  Files         141      141           
  Lines       11456    11456           
  Branches     2114     2114           
=======================================
+ Hits         9516     9517    +1     
+ Misses       1609     1607    -2     
- Partials      331      332    +1     

see 2 files with indirect coverage changes

[adithyaakrishna]

@dkoes Fixed CI and Updated CodeQL Workflow as well :)

[dkoes]

This is still broken. You need to rerun the CI build so that you can see what happens when the cache is populated.

[adithyaakrishna]

@dkoes I don't have permission to rerun workflow for this specific PR, but I ran it on my fork's branch and the cache works now.

Fork's Branch Action Runs

• https://github.com/adithyaakrishna/3Dmol.js/actions/runs/5337141144
• https://github.com/adithyaakrishna/3Dmol.js/actions/runs/5337186514
• https://github.com/adithyaakrishna/3Dmol.js/actions/runs/5337364845

Could you please rerun the workflow for this PR?

[dkoes]

Why?

[adithyaakrishna]

I found a pretty good blog related to improving jest test speeds, https://dev.to/vantanev/make-your-jest-tests-up-to-20-faster-by-changing-a-single-setting-i36 and according to it --runInBand is useful in resource-constrained environments like CI, where the overhead of worker processes is higher than the speedup of running tests in parallel.

[adithyaakrishna]

I also benched the tests using https://github.com/sharkdp/hyperfine and these are the results that I got. Over the course of 3-4 runs, --maxWorkers=50% seemed to be faster