feat(programming-language-support): Add xbase

[andreacfromtheapp]

📑 Description

Moving XBase to its own plugin as suggested by @Uzaaft . There is also a discussion about Swift/Xcode/Xbase/Xcodebuild here: #669

ℹ Additional Information

This changes (moving XCode baed tools to plugins instead of Swift pack) would require to remove the current Swift pack or if acceptable merge an opinionated version (when it manage to fix it...): #670 -- I'm fine deleting it altogether if this is not adhering to community standards. I'm not agreeing on having a Swift pack with only treesitter in there...

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

[andreacfromtheapp]

ps: nvimcraft didn't have a fitting category. as per contributing documentation I came up with one. I'm open to ideas and changes.

[Uzaaft]

We've got packs with only treesitter stuff, so that's not an issue tbh.

[andreacfromtheapp]

We've got packs with only treesitter stuff, so that's not an issue tbh.

I see. Well, I'm not in a position to decide on this. I still don't really agree with that, but I guess that's what it is.

[Uzaaft]

We've got packs with only treesitter stuff, so that's not an issue tbh.

I see. Well, I'm not in a position to decide on this. I still don't really agree with that, but I guess that's what it is.

It is what it is indeed.

I'll be going trough your PR later today.

[Uzaaft]

@gacallea Moved the plugin to what I think is a more sensible folder.

[andreacfromtheapp]

closes #669