feat(go): replace nvim-neotest/neotest-go with fredrikaverpil/neotest-golang

[Mega31]

📑 Description

• the golang adapter for neotest is outdated and does not even supports proper table driven testing(output is really messy)
• Adapter written by fredrikaverpil is much better and has many features which community would love https://fredrikaverpil.github.io/neotest-golang/

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

nvim-neotest/neotest-go#52 (comment)
Yeah, neotest-go doesn't have much resources to be updated.

PR title needs changing, since it's a breaking change and needs to mention which pack. Probably it's even a feature, since it might offer different functionality.

[Mega31]

nvim-neotest/neotest-go#52 (comment) Yeah, neotest-go doesn't have much resources to be updated.

PR title needs changing, since it's a breaking change and needs to mention which pack. Probably it's even a feature, since it might offer different functionality.

How is that a breaking change? I mean it just works

and I don't think it's a feature too, it simply extends functionality and makes overall things better?

[Mega31]

nvim-neotest/neotest-go#52 (comment) Yeah, neotest-go doesn't have much resources to be updated.
PR title needs changing, since it's a breaking change and needs to mention which pack. Probably it's even a feature, since it might offer different functionality.

How is that a breaking change? I mean it just works

and I don't think it's a feature too, it simply extends functionality and makes overall things better?

nvm it is a feature from astronvim pov. I have updated commit message now, hope it's okay

[Uzaaft]

@Mega31 PR title is still incorrect. Fixed it.

[Uzaaft]

@Mega31 Wanna give it a last test run before we merge this in?

[Mega31]

@Mega31 Wanna give it a last test run before we merge this in?

yep

[Mega31]

@Uzaaft just tested out. works fine

[azdanov]

Thanks!