Currently, {$_internalKeyStringValue} has no input size validation or memory limits and is available to the public, despite the {_internal} prefix. We cannot restrict access beyond setting `apiStrict` to false (which should be done in a follow-up ticket), so we must add memory limits. Add a new parameter internalQueryKeyStringValueMaxCollationBytes settable at startup and runtime that limits how much memory _internalKeyStringValue can use.