[M123] content: make disable-jit actually disable high-tier v8 compilers

As of r1247811, there is a new site setting, which is entitled "Sites
can use the V8 optimizer". The actual behavior of that setting, though,
is that it disables *all* use of JIT in the renderer, which means
disabling WebAssembly support altogether.

Since M122 is going to stable imminently, this change is the minimal fix
to avoid breaking an existing web API (wasm): the site setting's
behavior is changed to match what the settings page describes. Since
this setting is *also* tied to enterprise policies:

* DefaultJavaScriptJitSetting
* JavaScriptJitAllowedForSites
* JavaScriptJitBlockedForSites

This change will cause a behavior change for users of those policies:
webassembly will be enabled for sites for which it would previously have
been disabled.

(cherry picked from commit 89ec7fafe974099abf521610609545c594adeac4)

Fixed: 325974501
Bug: 325992828
Change-Id: If21f7e7b386ca3c682b5b2c0b7975001d2687651
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5310561
Reviewed-by: Will Harris <wfh@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Commit-Queue: Elly FJ <ellyjones@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1263023}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5318578
Commit-Queue: Ken Buchanan <kenrb@chromium.org>
Auto-Submit: Elly FJ <ellyjones@chromium.org>
Cr-Commit-Position: refs/branch-heads/6312@{#59}
Cr-Branched-From: 6711dcdae48edaf98cbc6964f90fac85b7d9986e-refs/heads/main@{#1262506}

• content/browser/renderer_host/render_process_host_impl.cc[diff]