CRITICAL: DO NOT IMPLEMENT THIS IF
WFCORE-2858 IS NOT IN PLACE. Otherwise existing behavior will regress.
Subtask for the following item from the parent issue:
JcaCachedConnectionManagerDefinition.CcmOperations has two operations that are not declared to be read-only that are registered on the profile resource. So these are pre-existing ops that break the no-runtime-only-on-profile rule that
WFCORE-389is about rescinding. A twist with these is they seem to actually be read-only and should be described as such. But if we do that we must implement WFCORE-2858to avoid breaking existing behavior.