The current per WebDriver session state for the capabilities acceptInsecureCerts and proxy has to be moved to a global state.

That means only the first created WebDriver session will evaluate these capabilities, and can install the certificate override or sets the proxy settings. For WebDriver sessions as created at a later time (while the first session is still active) the capabilities will be ignored during capability matching.

Note that we don't actually want to ignore the capabilities, we want to check that they match the existing state if it's already set. Presumably the state is already global, so we maybe just need to compare to that state (and maybe differentiating an "unset" state) rather than setting it unconditionally.

Lets actually remove it from M3 because it's not related to navigation. We will come back to it once we have requirements for allowing WebDriver BiDi clients to directly connect.