Check kOriginKeyedProcessesByDefault

[uazo]

Preliminary checklist

• I have read the README
• I have searched existing issues for my feature request. This is a new issue (NOT a duplicate) and is not related to another issue.
• I have searched wont fix issues and this request is not among them
• This is a feature request for the Cromite browser; not the website nor F-Droid nor anything else.

Is your feature request related to privacy?

Yes

Is there a patch available for this feature somewhere?

n/a

Describe the solution you would like

verify the difference between current management "Strict site per process + do not reuse processes" and "Origin-keyed Processes by default":

Enables origin-keyed process isolation for most pages (i.e., those
assigned to an origin-keyed agent cluster by default). This improves
security but also increases the number of processes created. Note:
enabling this feature also enables 'Origin-keyed Agent Clusters by
default'.

OriginKeyedProcessesByDefault (or "Origin Isolation (OI)" for short) is 
a new Chromium security feature that increases the process isolation to 
be based on origin, and not site. Since this will require more resources 
(higher process count), this feature will not be enabled by default on 
Android or low-memory desktop devices. But it is necessary to maintain 
test coverage for both the case where OI is not enabled by default (this 
corresponds to the current "site-isolation" case), and those where it is 
on. This will be done by having the OI-enabled case run tests on a CI 
builder that is monitored by the sheriffs. There are OI-specific tests 
that run on the regular builders, but the proposed new builder will run 
specified suites of tests with the OI feature enabled. 

ref. https://issues.chromium.org/issues/40259221

Describe alternatives you have considered

n/a