feat(go): change ray-x/go.nvim back to olexsmir/gopher.nvim

[rami3l]

📑 Description

Not sure about x-rayz plugins… Most plugins are a bit messy @luxus in https://github.com/AstroNvim/astrocommunity/pull/325#issuecomment-1612466608

Honestly at this point, I'm more eager to just purge go.nvim @Uzaaft in https://github.com/AstroNvim/astrocommunity/issues/1044#issuecomment-2178662610

Reverts #325, superseding #1054.

ℹ Additional Information

We're moving towards fewer included batteries, but I believe the stability outweighs features, and hopefully we can get them back via astrocommunity if the community really needs them.

[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

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

[rami3l]

Closing in favor of #1059. (Thanks, @mehalter!)