chore: Restore cypress libraries from cache rather than rebuilding in ci

[Zeyber]

Closes: https://jira.tools.sap/browse/CXSPA-12224

Notes:

• Checked job lengths.
  • A11y test suites themselves complete in under a minute.
  • Duration seems to be affected most by setup times.
  • B2C jobs seem to be the most impactful on duration. A11y jobs run in parallel to b2c so don't seem to impact total job duration.
  • A11y jobs also don't record in cypress dashboard. So job length seems to be misrepresented.
• Tested if the order matters for job sequence in the yml file (ie. B2C => b2b => a11y / a11y => b2c => b2b).
  • Looking into this to see if resource allocation gets prioritized to earlier jobs first.
  • Looks like the order does not affect resource allocation.
• Looking into setup steps.
  • It looks like npm packages still get installed on e2e jobs rather than restored from the cache.
  • Testing if packages can be restored from cache instead and checking the impact on job duration.

[github-actions]

Merge Checks Failed

Please push a commit to re-trigger the build.
To push an empty commit you can use `git commit --allow-empty -m "Trigger Build"`

[github-actions]

Merge Checks Failed

Please push a commit to re-trigger the build.
To push an empty commit you can use `git commit --allow-empty -m "Trigger Build"`

[github-actions]

Merge Checks Failed

Please push a commit to re-trigger the build.
To push an empty commit you can use `git commit --allow-empty -m "Trigger Build"`

[cypress]

spartacus    Run #51971

Run Properties:   Passed #51971  •  400bb543e0 ℹ️: Merge 1a4188253e1d812ef1a6079b93fffa160bc64f29 into 437e5ba62ab0c2297f3a3a3c3eeb...

Project	spartacus
Branch Review	feature/cxspa-12224
Run status	Passed #51971
Run duration	11m 23s
Commit	400bb543e0 ℹ️: Merge 1a4188253e1d812ef1a6079b93fffa160bc64f29 into 437e5ba62ab0c2297f3a3a3c3eeb...
Committer	Caine Rotherham
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	3
Pending	0
Skipped	0
Passing	101
⚠️ You've recorded test results over your free plan limit. Upgrade your plan to view test results.
View all changes introduced in this branch ↗︎

[github-actions]

Merge Checks Failed

Please push a commit to re-trigger the build.
To push an empty commit you can use `git commit --allow-empty -m "Trigger Build"`

[github-actions]

Merge Checks Failed

Please push a commit to re-trigger the build.
To push an empty commit you can use `git commit --allow-empty -m "Trigger Build"`

[github-actions]

Merge Checks Failed

Please push a commit to re-trigger the build.
To push an empty commit you can use `git commit --allow-empty -m "Trigger Build"`

[github-actions]

Merge Checks Failed

Please push a commit to re-trigger the build.
To push an empty commit you can use `git commit --allow-empty -m "Trigger Build"`

[github-actions]

Merge Checks Failed

Please push a commit to re-trigger the build.
To push an empty commit you can use `git commit --allow-empty -m "Trigger Build"`

[github-actions]

Merge Checks Failed

Please push a commit to re-trigger the build.
To push an empty commit you can use `git commit --allow-empty -m "Trigger Build"`

[github-actions]

Merge Checks Failed

Please push a commit to re-trigger the build.
To push an empty commit you can use `git commit --allow-empty -m "Trigger Build"`

[github-actions]

Merge Checks Failed

Please push a commit to re-trigger the build.
To push an empty commit you can use `git commit --allow-empty -m "Trigger Build"`

[github-actions]

Merge Checks Failed

Please push a commit to re-trigger the build.
To push an empty commit you can use `git commit --allow-empty -m "Trigger Build"`

[github-actions]

Merge Checks Failed

Please push a commit to re-trigger the build.
To push an empty commit you can use `git commit --allow-empty -m "Trigger Build"`

[github-actions]

Merge Checks Failed

Please push a commit to re-trigger the build.
To push an empty commit you can use `git commit --allow-empty -m "Trigger Build"`