Use Rubygems Trusted Publishers to publish

[ydah]

Fix: https://github.com/rubocop/rubocop-rspec/issues/1827

---

Before submitting the PR make sure the following are checked:

• [x] Feature branch is up-to-date with master (if not - rebase it).
• [x] Squashed related commits together.
• [-] Added tests.
• [-] Updated documentation.
• [-] Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
• [x] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

[bquorning]

Ooh, maybe this workflow could also create a new GH Release after publishing a new version.

[ydah]

I updated this PR. How about this?

[pirj]

This is incredible! I’ve just been reading a story about xz-utils today, what they pushed as a release was different from the source code. I hope we reduce the possibility of this happening with such trusted publishing?

[bquorning]

After this PR is merged, #1859 will add automatic creation of GitHub releases with notes generated from the changelog. Less manual work for us 😅

Or @ydah if you prefer, feel free to cherry-pick my changes into this branch.

[ydah]

@bquorning Thank you 😄! Let's merge #1859. Then we will close this PR👍

[bquorning]

@ydah If you squash the two commits, we can merge this PR and I’ll rebase #1859.

[bquorning]

The final git push failed because of our branch protection rules: https://github.com/rubocop/rubocop-rspec/actions/runs/8561970997/job/23464311900

I don’t know if we can somehow override that.

[ydah]

Maybe, I think the solution is as follows.

• creating a service account user that has read-write access to repo
• create a pat for that service account
• add the service account to the bypass protection rules in the branch
• create a repo secret that contains the PAT token
• push using the created service account