[23.1] Disable console instead of dropping

[ElectronicBlueberry]

We are currently dropping all console commands from production builds.
This is desirable, as console commands can cause performance impacts and memory leaks.

However, it can make looking into issues on production a lot harder. Some useful vue errors, warning logs, or custom logs which could help in quickly pinning down an issue may be hidden.

This PR disables the console instead of dropping it, by overriding each key of the global console object with empty functions. It also adds the global functions enableDebugging() and disableDebugging(), which can be run from the console.

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[dannon]

+1, I actually ran into a situation recently where I ended up running a local client with CHANGE_ORIGIN just to debug. Powerful tool, but just enabling the console might have saved me some trouble.