feat(nvim): use codecompanion extension API.

[Davidyz]

olimorris/codecompanion.nvim#1290

example config:

opts = {
  extensions = {
    vectorcode = {
      opts = { add_tools = true, add_slash_command = true },
    },
  },
},

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.15%. Comparing base (397b6f6) to head (804845b).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #99   +/-   ##
=======================================
  Coverage   99.15%   99.15%           
=======================================
  Files          22       22           
  Lines        1423     1423           
=======================================
  Hits         1411     1411           
  Misses         12       12           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Davidyz]

@ravitemer hi I think I'm done here with the extension. If you're available, could you take a look at my implementation? Just want to make sure I did everything correctly before I merge.

btw this really setting things up A LOT easier. Thanks for the extension API!

[ravitemer]

@Davidyz It's perfect. Your way of not using the callback to point to the extension is even better.

Looks great to me!

[Davidyz]

Something I came across when writing this PR:
It might be worth adding to the documentation that extension devs should check for duplicated tool names etc. because it looks like the setup function might overwrite things without the users noticing.

[ravitemer]

Yes! I am guilty of that 😅. Will update the docs and mcphub extension.