Dependencies: Pin file-system-cache to 2.3.0

[JReinhold]

Closes #23220

What I did

Pinned the dependency file-system-cache to v2.3.0 to avoid the failing v.2.4.0 as reported in the issue.

This is the result of yarn why file-system-cache in code:

├─ @storybook/core-common@workspace:lib/core-common
│  └─ file-system-cache@npm:2.3.0 (via npm:2.3.0)
│
└─ @storybook/types@workspace:lib/types
   └─ file-system-cache@npm:2.3.0 (via npm:2.3.0)

How to test

Must be tested in a case-sensitive operating system like Linux - not MacOS or Windows.

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• If this PR should be tested against many or all sandboxes,
  make sure to add the ci:merged or ci:daily GH label to it.
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

[tremby]

The dependency author has fixed the issue so this could potentially be unpinned again now.

[seriouz]

Yes please use the new version 2.4.1 our pipeline broke with 2.4.0... But 2.4.1 is working again!