Memory-storage error handling for 'store not provisioned' and conflicts was consolidated and renamed internally
The internal client that talks to the memory-storage backend (used for listing, reading, creating, updating, and deleting memory data) now routes all of these operations through one shared helper that turns HTTP error codes, like 404, into a consistent typed error before any operation-specific handling runs. This replaces duplicated handling that previously existed separately for each operation. The internal error types for "store not provisioned" and "conflict" were also renamed.
This is an internal cleanup that makes error handling for memory storage more consistent across list, read, create, update, and delete operations, reducing the chance that one operation handles a missing store or a conflict differently from another.