Change Go module name to match repo

[vearutop]

🤔 What's changed?

This PR changes Go module name to match source repo.

⚡️ What's your motivation?

go mod tidy in a project with github.com/cucumber/messages/go/v19 import fails with

        github.com/cucumber/messages/go/v19: github.com/cucumber/messages/go/v19@v19.0.0-20221109131039-1b570700edc2: parsing go.mod:
        module declares its path as: github.com/cucumber/common/messages/go/v19
                but was required as: github.com/cucumber/messages/go/v19

🏷️ What kind of change is this?

• 🐛 Bug fix (non-breaking change which fixes a defect)

♻️ Anything particular you want feedback on?

📋 Checklist:

• I agree to respect and uphold the Cucumber Community Code of Conduct
• I've changed the behaviour of the code
  • I have added/updated tests to cover my changes.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
• Users should know about my change
  • I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

---

This text was originally generated from a template, then edited by hand. You can modify the template here.

[mpkorstanje]

Looks good. Two semi related questions:

1. What kind of change is this w.r.t Semver? It doesn't seem to break anything. So I'm guessing it's a fix. Is that correct?
2. We currently publish a subtree of the go directory to https://github.com/cucumber/messages-go, is this still nessesary?

[vearutop]

What kind of change is this w.r.t Semver? It doesn't seem to break anything. So I'm guessing it's a fix. Is that correct?

Yes, I suppose the code in this repo isn't currently accessible as a Go module (without custom replaces), so this PR is a fix (patch release).

We currently publish a subtree of the go directory to https://github.com/cucumber/messages-go, is this still nessesary?

I'm not sure, I think github.com/cucumber/messages-go was planned for deprecation (and maybe archiving), originally with the idea of replacing it with monorepo, now with this repo. So probably any automations/maintenance for messages-go could be disabled.