Adding wsl user start scripts

[jsboige]

Those script proved useful to automatically set up environment variables and port redirection without affecting the system scripts, which might be left untouched for git pulls, allowing for user customization as in Automatic1111. The multi-start is especially useful to launch a series of instances on distinct ports with distinct models. I'm planning to use it to add integration tests to this new SK connector, together with the Oobabooga connector, which is also a work in progress. I left actual values I have been using for reference, but feel free to adapt those values

[oobabooga]

Those are big changes that I am unable to review as I do not use WSL.

[jsboige]

Hi, I'm sorry this fell flat. Let me please plead why I think this could be useful.

• Using wsl, the port redirection to apply on each IP change was really a pain in the ass. And wsl proved the best solution for me with days lost on regular Windows install with gpu issues.
• The ability in Automatic1111 to craft custom user launch files while still updating the system launch scripts through regular pulls is a must.
• Finally, I think the multi-launch .bat is also really useful. I'm currently working hard to make Oobabooga a first class provider for Semantic Kernel. Part of that involves being able to offload ChatGPT to specific Oobabooga hosted models through a multi-model adapter. Launching several parallel instances of a single Oobabooga installation on distinct ports with distinct models works like a charm and the multi .bat script template proposed here is all I need to get it all running.

So those are 3 strong reasons to consider that PR.

Now I will be happy to do some more work and craft other .bat user files for other environments so that you can test them. What is your testing environment? @oobabooga, will you be OK to reopen this PR when you can test it?