Feature/storm 55

[zantvoort]

Entity Cache

• Enabled in read-only transactions.
• Disabled for READ_UNCOMMITTED to respect isolation semantics.
• Caching provides optimization without affecting correctness; versioning remains advised for concurrent updates.

Performance

• Cache / interner lookup extracts primary key before construction, avoiding full entity equality checks.
• Interner uses primary key based lookups instead of equality checks for entities.
• Interner is used when entity cache is not applicable and is scoped to the result set to prevent duplicate objects.
• Queries returning the same entity within a result set or transaction benefit from caching / interning.

Relates to #55