refactor(completion): update AI plugins to use the new `astrocommunit…

[mehalter]

…y.recipes.ai` boilerplate

📑 Description

This is an exploration of using the new AI recipes in AstroCommunity to improve the maintenance and implementation of AI plugins with completion. This should be tested, improved, and iterated on before merging. Someone could figure out a nice way to have the user switch between inline suggestions vs completion based suggestions using the vim.g.ai_inline variable that the user can set in AstroCore

ℹ Additional Information

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

A bit difficult to imagine how to make it work across so many different plugins, since I lack experience with many of them. 🤔

My main ones are just github/copilot.vim and CopilotC-Nvim/CopilotChat.nvim.