ParsedDataStorageManager

The full parsed-data store: queryable, writable, persistable, plus access to its internals.

This composes four concerns rather than declaring 22 methods itself, so that each consumer can name the one it actually needs:

• {\StubTests\Framework\Storage\StubDataQueryInterface} — reading entities (what validators get)
• {\StubTests\Framework\Storage\ParsedDataWriter} — adding entities and processing them (what the parsers get)
• {\StubTests\Framework\Storage\ParsedDataPersistence} — save()/load() (only the cache-generation paths)
• the accessors below — the backing provider and the pipeline, for wiring and tests

The composite still exists because DefaultParsedDataStorageManager is all four things, and the cache-generation scripts legitimately use all four in sequence: build, process, save. What changed is that nothing else has to accept all four — Runner::getStubs() and getReflection() now return the read interface, so a validator holding one cannot call save() or load() on the committed cache.