feat(completion): add codeium-cmp plugin

[khas-amir]

📑 Description

Add native codeium plugin for neovim

ℹ Additional Information

[github-actions[bot]]

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

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

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

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

[khas-amir]

@Uzaaft why ?

[Uzaaft]

Nevermind, turns out the plugin doesn't provide virtual_text stuff. What a shame.

[Uzaaft]

@khas-amir We'd appreciate it if you next time follow the conventionsin this repository.

[Uzaaft]

Removed mapping that didn't make sense at all. Should be good to go now

[Uzaaft]

Just tested before I merged this, and seems like the cmp lazy loading isn't working 🫠

[Uzaaft]

Should be working now. @khas-amir Can you test before I merge this?

[khas-amir]

@Uzaaft everything works on my arch linux

[khas-amir]

community.lua

return {
  { "AstroNvim/astrocommunity", dev = true },
  { import = "astrocommunity.colorscheme.catppuccin" },
  { import = "astrocommunity.motion.nvim-surround" },
  { import = "astrocommunity.pack.lua" },
  { import = "astrocommunity.pack.rust" },
  { import = "astrocommunity.pack.typescript" },
  { import = "astrocommunity.pack.tailwindcss" },
  { import = "astrocommunity.completion.codeium-nvim" },
}

``` `