chore: always bump the patch version for main releases

Description

This MR improves our release process by allowing us to always publish a main release by overriding the versioning logic used in the commit-analyzer semantic-release plugin.

We always return at least a 'patch' version update for main releases, thus ensuring we can always publish one, even if the only changes that have been done are chores that would not trigger a release otherwise.

pre-releases are still skipped if there are no changes.

This MR resolves #1917 (closed).

Related Issues

Resolves #1917 (closed)

How has this been tested?

I've tested this approach in my private repository fork

Here's how the pipelines look:

And releases page. Note the main release creates an entry in the changelog with no additional text. I think that's how we did it when we wanted to force a release after a pre-release happened:

• If src/browser or src/common has been modified, please consider interoperability with the Web IDE. See Running the Extension in WebIDE.
• Consider an end-to-end test for significant new features that aren't covered by integration tests.

Screenshots (if appropriate)

What CHANGELOG entry will this MR create?

• fix: Bug fix fixes - a user-facing issue in production - included in changelog
• feature: New feature - a user-facing change which adds functionality - included in changelog
• BREAKING CHANGE: (fix or feature that would cause existing functionality to change) - should bump major version, mentioned in the changelog
• None - other non-user-facing changes