Implement custom remote script support for Linux remotes

[StarLederer]

This PR makes it so that server setup scans the remote for known remote installer locations before attempting to use built in scripts.

This allows users to:

• Use any format (bash, tchs Cannot install server on host whose default shell is tcsh #100, js, python, or even compiled binaries).
• Install servers binaries to custom locations Is it possible to have only one server directory for multiple users? #35.
• Use any version of wget they need Could not establish connection: Error resolving authority, wget options not supported on linux x86_64 OpenWRT system using busybox, how to remove them? #116,
• Support downloading the server from IPFS.
• Patch server binaries for unusual systems (existing tools are unnecessarily complex).
• Implement other remote-side features that are undiscovered yet without having to request changes in this extension FR: Server setup hooks #120.

[StarLederer]

If this is welcome, we possibly need to document how to write custom scripts or make the default one work the same as custom

[jeanp413]

Thanks for the PR @StarLederer 🙏 , can we add a extension setting like remote.SSH.customServerInstallScriptPath and use that instead of harcoding it, also a new command like Customize Server Installation Script and then open a vscode document and initialize it with the default script content that the user can edit and save.

[StarLederer]

I figured using conventional paths would be best for users so they don't have to think how each remote is configured, just whether it explicitly supports open-remote-ssh or not. It is possibly a good idea allow users to override this per host so that their host providers are able to escape the conventional structure if they really need to but I imagine this being more the exception than the rule.

As per hard-coded paths vs configurable defaults, I see how in the future the MS extension might also adopt this and use different paths than us but I would add an option to change the default paths only when that happens. I think if users identify missing but expected paths, like something for windows hosts, it is better to add these paths to the extension to help users find the conventional way to organize this and use this extension seamlessly across many remotes. Let me know if you agree.

I really like your Customize Server Installation Script idea though, it will give users an example that they can start messing with right away and make it very easy to find where to put the config avoiding the need for extra documentation, but I have no idea how to implement this. VS Code extensions are far from my expertise. Perhaps that could be a separate PR that we collaborate on?