fix: webContents.openDevTools({mode}) not working

[codebytere]

Description of Change

Closes #32702.

Electron calls into UI.DockController.instance().setDockSide(side) in order to allow users to set the devtools dock position via webContents.openDevTools({ mode }). In this DevTools CL the globals which we used to enable this were removed, and so we need to re-expose them to fix this broken functionality. We should look to upstream a more durable approach to allowing us to do this.

Tested by adding mainWindow.webContents.openDevTools({ mode: 'left' }) to the default stock Fiddle and observing that it no longer errors and the devtools docks appropriately to the left-hand side.

Checklist

• PR description included and stakeholders cc'd
• relevant documentation is changed or added
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Fixed an issue where webContents.openDevTools({ mode }) did not work for certain dock positions.

[nornagon]

hrm. Chrome manages to open devtools on a particular side without this hack. How does it work in Chrome?

[codebytere]

@nornagon to my knowledge it's never done programmatically - it's done here via button click listeners.

[MarshallOfSound]

We should find a better way but this isn't awful

[release-clerk]

Release Notes Persisted

Fixed an issue where webContents.openDevTools({ mode }) did not work for certain dock positions.

[trop]

I have automatically backported this PR to "17-x-y", please check out #32945

[trop]

I have automatically backported this PR to "18-x-y", please check out #32946

[dsanders11]

@zcbenz @codebytere, looks like this landing broke gclient sync on CI due to the patch.

[zcbenz]

Thanks for noticing it, I created a PR at #32950.