Release workflow

[payalkanyan]

Description

The release workflow is added

What does this PR do?

This adds the release workflow for the repo

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• New chore (expected functionality to be implemented)

Checklist:

• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
• I've signed off with an email address that matches the commit author.

[mathieu-benoit]

Thanks @payalkanyan for your contribution.

It turned out that the release process is like this:

• Create a tag/release in there https://github.com/score-spec/score-go/releases by one of the core maintainers
• Then, a few hours after it's synced in there https://pkg.go.dev/github.com/score-spec/score-go to be used/consumed

So we don't need any automation in addition to what's in place already. Sorry for the confusion in the associated issue at the first place! Closing this one and updating the associated issue: #52.

Thanks again!