feat: support multiple config names in :LspStart

[toupeira]

Description

Problem:
The arguments for :LspStart and :LspStop are inconsistent, the latter supports multiple arguments while the former only takes one or zero arguments.

Solution:
Support multiple config names in :LspStart as well.

Context

• Follow-up from fix: restore :LspStart/LspStop behaviour without arguments #3890 (comment)

[justinmk]

I would prefer that neither of them supported multiple args. What is the use-case? These commands should not be used in scripts. Interactive usage is typically not going to specify multiple names.

Scripts should use vim.lsp, not these commands. Commands are for interactive use.

[toupeira]

@justinmk that sounds good to me too, I just added this for consistency with the LspStop and LspRestart commands.

I personally don't have a use case, but I'm also not sure if we should change the behaviour of LspStop / LspRestart now since I guess that would technically be a breaking change. Maybe I should leave this alone, and then any new behaviour can be implemented in the upstreamed :Lsp multi-command?

(if you agree feel free to close this PR 😀)

[justinmk]

but I'm also not sure if we should change the behaviour of LspStop / LspRestart now since I guess that would technically be a breaking change.

We should make that change. The goal is to get the code in shape and then upstream it to core Nvim.