feat(lsp): added dev-tools.nvim

[YaroSpace]

📑 Description

Add utility (LSP):

In-process LSP server of custom code actions, enhanced actions picker, community actions library and a convenient interface for customization and enhancement of your Neovim with custom code actions.

[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)

• Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).

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

• Proper usage of specs table for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).

[azdanov]

Looks good, thanks!

@Uzaaft Could you also please have a look? Maybe there's something I'm missing.

[Uzaaft]

Ideall, we would have used astrolsp to handle the "LSP"(Im not sure your usage of the term is the correct one). But this is the best we can do for now

[YaroSpace]

Thank you, guys! 👍

[Uzaaft]

Thank you, guys! 👍

thank you for the PR. :) I see you also have other plugins, perhaps they can be added? 😉