JS Release Tool / Breaking Change Detection May Fail Due to Accidentally Published Deprecated Versions

### Background
During 8/21–8/22 2025, pipeline issues caused many nightly builds to be incorrectly published as GA/beta versions to npmjs. These versions were subsequently deprecated and do not have corresponding changelog entries.

### Problem
The accidentally published versions initially had no matching GitHub tags, which caused the check-package-version step to fail when determining whether a package version should be incremented after changes are made to files under [src](vscode-file://vscode-app/c:/Users/v-zhanh/AppData/Local/Programs/Microsoft%20VS%20Code/1b50d58d73/resources/app/out/vs/code/electron-browser/workbench/workbench.html).

The missing tags have since been recreated and pushed to GitHub, so the deprecated GA/beta versions now have matching tags. However, these versions still lack changelog entries since their releases were unintentional.

### Impact
Many packages may now be in a state where:

- The last published GA/beta version is deprecated
- There is no changelog entry matching that version

This can affect:

- JS release tooling
- Breaking change detection logic
- Any downstream logic that relies on the last published version having a valid changelog entry