chore: bring back force-version-update plugin

Andrei Zubovrequested to merge
azubov/bring-back-forced-patch-update-for-release into main

Description

force-version-update inline plugin ensured we can always release vscode even if no release-triggering commits were added.

It was removed as there were an exhaustive list of commit types added as would trigger a release, but apparently it's not enough 🤔

Bringing back the inline plugin should ensure the release is always triggered.

Related Issues

Resolves #[issue_number]

How has this been tested?

  • 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

Merge request reports