FEAT Less cache fragmentation in ClassManifest

[lekoala]

Description

Reduce cache fragmentation by having only one entry for all cached files

Manual testing steps

Check number of files being created

BEFORE: 2k files

AFTER: 3 files

Issues

#11525

Questions

Should this target 6 ? for me, while this is technically a new "feature" it has only upsides and also "fixes" a performance issue

Pull request checklist

• The target branch is correct
  • See picking the right version
• All commits are relevant to the purpose of the PR (e.g. no debug statements, unrelated refactoring, or arbitrary linting)
  • Small amounts of additional linting are usually okay, but if it makes it hard to concentrate on the relevant changes, ask for the unrelated changes to be reverted, and submitted as a separate PR.
• The commit messages follow our commit message guidelines
• The PR follows our contribution guidelines
• Code changes follow our coding conventions
• This change is covered with tests (or tests aren't necessary for this change)
• Any relevant User Help/Developer documentation is updated; for impactful changes, information is added to the changelog for the intended release
• CI is green

[GuySartorelli]

Can you please throw some benchmark numbers at me to help understand what the actual performance impact of this change is (either in terms of time or memory)?