fix(swift): fix LSP handler error

[andreacfromtheapp]

📑 Description

fixing an issue where:

• enabling { import = "astrocommunity.pack.swift" },

• enabling lsp = { servers = { "sourcekit"} } (not installed with mason)

• would trigger this error:

[lspconfig] Cannot access configuration for sourcekit-lsp. Ensure this server is listed in "server_configurations.md" or added to a custom server.

[github-actions]

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

• If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

• If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

• Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

• README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

• Proper usage of opts table rather than setting things up with the config function.

[andreacfromtheapp]

After some considerations and comments from @Uzaaft I gave it another try. here's what works:

1 - pack/swift/init.lua with only xbase (sourcekit line restored with changes, null-ls removed) + treesitter + dap
2 - no lsp config in user/init.lua needed
3 - swiftformat + swiftlint added to user/null-ls.lua (adding them to the pack was opinionated)

notes: if null-ls is present in pack/swift only it won't use them for some reason, two birds with a stone: unopinionated + user defined == this way the change is minimal, unopinionated and 100% working 🙂

I hope this helps. If I made mistakes I apologize. If this is bad somehow, feel free to refuse it. I won't take it persoally :)