[FEATURE] Debugger support scripts with inspection tools

[commandblock2]

LiquidBounce Branch

Nextgen

Describe your feature request.

Since we are using graalvm, we might have a chance to use its debugger support for our scripts. Using this will require one more external dependency, chromeinspector. Generally I am looking for possibility for placing breakpoints and having REPL. You can assign this to me.

Additional context

No response

[commandblock2]

this is easily proven to be feasible, there are details like event being shown as undefined even though you can unfold it and see what member is in the object or typing in the debug console will sometimes result in very long exception reporting like below. Or the evaluation cannot be done when the game is not paused.
.

Since LBNG does come with a mcef browser, we might be able to direct a developer tool page or something to help debugging a script without any external tools and a built-in setting for if a certain script module should be loaded in debug mode?

Also a it might enable us to add a repl module for quickly debugging whatever you would like to try.

[commandblock2]

going to try oracle/graal#5844 (comment) to see if it works

[commandblock2]

I was able to use the lsp option and got it running, here is a capability reply from the lsp server, but in the initialize request it was not using the right workspaceFolders, not sure if it has anything to do with that
part of the request from vscode:

            "workspaceFolders": [
                {
                    "uri": "file:///mnt/old-linux/home/commandblock2/git_repo/MultiMC5/build/instances/LBNG-Production/minecraft/LiquidBounce/scripts",
                    "name": "scripts"
                }
            ]

response from the lsp of graalvm

{
    "result": {
        "capabilities": {
            "hoverProvider": true,
            "workspaceSymbolProvider": false,
            "completionProvider": {
                "resolveProvider": false
            },
            "referencesProvider": false,
            "definitionProvider": false,
            "documentHighlightProvider": true,
            "codeActionProvider": true,
            "signatureHelpProvider": {},
            "textDocumentSync": 2,
            "documentSymbolProvider": false,
            "codeLensProvider": {
                "resolveProvider": false
            },
            "executeCommandProvider": {
                "commands": [
                    "dry_run",
                    "get_coverage"
                ]
            }
        }
    },
    "id": 0,
    "jsonrpc": "2.0"
}

[commandblock2]

Also the chromium browser comes with mcef does not seems to bundle a devtools:// you may found in a regular chromium. So if we want in-client debugging it's very likely that we will have to serve it ourself.