feat(completion): Add vim-tabby

[PatMulligan]

Closes #872

📑 Description

Instructions to use Tabby for an open-source, self-hosted AI coding assistant. With Tabby, every team can set up its own LLM-powered code completion server with ease.

• Install TabbyML/vim-tabby with Lazy
• Set proper initial config (non-conflicting key-bindings, etc)
• Clean up README

Additional Information

I added some steps for installing on Linux with Docker as Tabby Docs demonstrate particularly methods for Windows/Mac. However, maybe this is more suited to putting in their repo? Or maybe the user is just expected to figure this out on their own as Docker is agnostic... Let me know what you think

Otherwise, just want to make sure that the key-bindings are appropriate. I assume is likely to be conflicting...

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

[Uzaaft]

See comments I added.

[Uzaaft]

So the only thing missing is to fix the keybindings. Any proposals?

[Uzaaft]

I'll add the mapping to astrocore later today.

[luxus]

How does it gets loaded if lazy is true?

[mehalter]

we don't set lazy = true

[mehalter]

If the user wants lazy loading then they can add it themselves. Or someone can recommend a good default lazy loading scheme

[luxus]

yeah sure, but most specs here have some trigger for loading, i guess people would expect it would work if they setup lazy = true
or does event = { "AstroFile" } not make sense in this case?

[mehalter]

sure we can set that event i don't think it makes a different really

[PatMulligan]

with the addition of event = "User AstroFile", the Tabby server seems not to connect for some reason, it stalls at initializing, but can't seem to find any logs. Would this modify the runtimepath in anyway?

Not valid anymore