We currently have a setting storage.mvcc.max_intents_per_error that limits the number of intents included in WriteIntentError during e.g. scans and exports. This defaults to 5000, which is fairly large, so we should consider an additional byte limit to avoid OOM situtations when encountering large intents.

Jira issue: CRDB-11210