Create SnapshotCacheReadOnly for read only snapshots

[shargon]

Description

Avoid reusing the same class for different purposes.

Type of change

• Optimization (the change is only an optimization)
• Style (the change is only a code style for better maintenance or standard purpose)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Current

Test Configuration:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[cschuchardt88]

Evite reutilizar la misma clase para diferentes propósitos.

I think you mean Avoid reusing the same class for different purposes.

[Jim8y]

LMAO, we have too many of these, please in the future try to make them reusable when we have time.

[cschuchardt88]

Why don't you expand other interfaces? We are not going to have 50 classes for caching now are we? This is already out of hand. But now its getting worse.

[shargon]

I will do a different thing

[nan01ab]

Why not IReadOnlyStoreView?