Update release process

What does this MR do and why?

There were some issues with the latest release attempt:

1. npm publish failed (https://gitlab.com/gitlab-org/glql/-/jobs/11951905534), but it doesn't say why as it had --silent flag. Also the job was allowed to fail (not sure if intentionally ), so it still tried and go ahead with the gem release. I've confirmed that npm doesn't contain the updated version: https://www.npmjs.com/package/@gitlab/query-language-rust?activeTab=versions
   1. Update: This is caused by issues with npm token https://gitlab.slack.com/archives/CH9QG9TAQ/p1760711413620929
2. The gem-release jobs were not triggered correctly after the automated version bump commit. This seems to have to due with the fact that the gem-release jobs works correctly when triggered from an MR rather than a push direct to main.
3. There was a prettier-linting error in the Changelog that caused a job failure

Changes in this MR:

• Revert version bump, which did not go through (950cc851)
• Change the release script so that it creates a separate MR version bump for the ruby gem. We can follow up on this by aligning the npm release with the same MR-based process, or fix the gem-release jobs to work with direct pushes to main
  • Sample MR: !300 (closed)
• Fix the linting error by excluding Changelog from prietter linting
• Make the npm publish job fail ( and remove --silent option for better logging)

Related to gitlab#573055 (closed)