fix: set the gemspec version using the release tag value

[Eazybright]

This PR updates the release.yml to include a step to automatically sets the version of the SDK to be published using the value of the release tag.

[unicodeveloper]

@Eazybright I just tried to tag a new release.

We have an error for it trying to set up Ruby. Check here: https://github.com/novuhq/novu-ruby/actions/runs/6484505880/job/17608488730#step:4:38

[unicodeveloper]

I can see that the gem.lock file here supports only universal Java 17 and that's why we have that error

https://github.com/novuhq/novu-ruby/blob/main/Gemfile.lock#L91

[Eazybright]

@unicodeveloper i've raised a PR for the fix: https://github.com/novuhq/novu-ruby/pull/47

[unicodeveloper]

@Eazybright I just tried it again. The java platform issue has been fixed correctly. But we have another issue now.

This is the action log: https://github.com/novuhq/novu-ruby/actions/runs/6490687700/job/17626846860

So for some reason, it is not using the new version number gotten from the tags to publish to Rubygems. It's still using the gemspec file version number.

[unicodeveloper]

Never mind. I'll fix it. I think I have figured out what to do.

[unicodeveloper]

A new release has been tagged 🍾 🎊 . The process to release a new version now is:

• Update https://github.com/novuhq/novu-ruby/blob/main/lib/novu/version.rb with the new version that we want to tag
• Tag a new release on GitHub
• Workflow kicks in and automatically pushes the new version to Ruby gems.

[Eazybright]

https://github.com/novuhq/novu-ruby/pull/46#issuecomment-1758915278

great work @unicodeveloper