Cache Reading and Writing Mismatch

[GCHQDev404]

Describe the bug
A cache reader hook NamedViewResolver or NamedOperationResolver could be configured with a cacheSuffix different to the a cache writer handler AddNamedViewHandler or AddNamedOperationHandler.
Previously there was a Logger error, but this can be ignored or missed, and there is no reason for such behaviour.

To Reproduce
Steps to reproduce the behavior:

1. Create a graph with a graphConfig containing a Resolver Hook with no suffix or suffix different to what is specified in the OperationDeclarations file.
2. turn on the graph

Expected behavior
Exception explaining the cache suffix naming mismatch.

Additional context
CacheSuffix naming has been improved to isolate the different types of caches and which names should match.
If no suffix is used then properties or last the graphId is used.