Extend crash string length to 256 for ProcessLocks process misuse.

ProcessLock.ToString() has grown in size with information such as their
cross-origin isolation status and locked origin. To be able to record
the full information the crash keys need to be bumped to 256B.

Bug: 1142391
Change-Id: Ibdedf81ef4315248337b323734c8241361a8fbea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2502331Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Commit-Queue: Arthur Hemery <ahemery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#821717}

content/browser/renderer_host/render_frame_host_manager.cc

@@ -905,7 +905,7 @@ RenderFrameHostImpl* RenderFrameHostManager::GetFrameHostForNavigation(
       !request->IsForMhtmlSubframe()) {
     base::debug::SetCrashKeyString(
         base::debug::AllocateCrashKeyString("lock_url",
-                                            base::debug::CrashKeySize::Size64),
+                                            base::debug::CrashKeySize::Size256),
         process_lock.ToString());
     base::debug::SetCrashKeyString(
         base::debug::AllocateCrashKeyString("commit_origin",