[Feature] Automate Go SDK release process

[dyeam0]

Checklist

• I agree to the terms within the OpenFGA Code of Conduct.

Describe the problem you'd like to have solved

Currently, the go-sdk requires manual intervention for versioning and tagging. This manual overhead includes version update and release tag creation. This creates friction that slows down the delivery of features and fixes.

Following the initiative described in parent SDK generator issue openfga/sdk-generator#679, we want to automate the process so the SDK is always in a deliverable state, and releasing a new version is as simple as a single manual trigger.

Describe the ideal solution

The solution implements logic for Go-specific artifacts and workflows necessary to support the automation requirements outlined in the parent issue. While the core logic is handled by the SDK generator, this repository must manage the specific mechanics of the Go ecosystem.

Implementation Points:

• Release Tag Management: Implementation must ensure that semantic version tags (ex., v0.7.x, v1.x.y) are used and follow package conventions.
• Ecosystem: The workflow should ensure the new release package is correctly indexed and discoverable.
• GitHub Release: Automate the creation of the GitHub Release tied to the new tag, incorporating the generated changelog as described in the parent issue.
• Changelog: The automated changelog should be seamlessly included in the GitHub Release notes during the tag creation process.

Alternatives and current workarounds

See parent: openfga/sdk-generator#679

References

No response

Additional context

No response