perf(experimental): if fsCacheModule is enabled, read from the memory when possible

[sheremet-va]

Description

WITHOUT the flag:

   Duration  143.61s (transform 42.52s, setup 137.49s, collect 512.51s, tests 391.96s, environment 184.77s, prepare 4.08s)

WITH the flag for the first time (NOTHING is cached):

   Duration  143.20s (transform 31.37s, setup 133.52s, collect 518.19s, tests 392.79s, environment 180.64s, prepare 4.18s)

WITH the flag for the second time (ALL is cached):

   Duration  139.24s (transform 9.82s, setup 134.87s, collect 493.98s, tests 377.08s, environment 181.94s, prepare 4.20s)

Conclusion: the cache is good for small scale testing (one or a few tests during development), but is pretty negligible when running the full suite. One other thing that could help here, perhaps, is a different sorting algorithm

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.
• Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.