Release Automation Improvements

[SydneyhSmith]

We should clean up/optimize the release automation for the VSCode extension in order to reduce the time dedicated to each release so that we can optimize our time for improving the extension and release at a more frequent cadence.

cc: @rjmholt @andschwa

[rjmholt]

We should slurp up any relevant parts of #2286 into this issue and close that one

[andyleejordan]

I'm actively working on this now as I want to be able to get releases out without pulling my own hair out.

[andyleejordan]

@rjmholt I have like 3 remaining bullet points to do, I'll get those in before merging the PR.

[andyleejordan]

Uhh wtf my bulleted list of tasks are gone. Well, I made a new issue for the remaining piece, plus there's to delete the 'vses' scripts after we're happy with the pipeline.

[andyleejordan]

I think GitHub's having issues, adding this as I found it in an unrefreshed tab:

• Handle merge PRs (not just squashes)
• Sub out GitHubTools with PowerShell for GitHub
• Fix version scripts (package.json, lock file, psd1 all need to be bumped) Moved to Add Update-Version to ReleaseTools module #3268
• Fix publishGH to handle emoji changelog
• Force-update branch (so changelog generator can be re-run) Chose not to do, not worth the trouble
• Handle “v” prefixes and “-preview” suffixes
• Misuses URL when it can’t find the right one
• Replace VSES vars with trigger (after testing) Need to test internal release pipelien
• Fix publishGH to find correct repo’s changelog
• Delete old script
• Add pipeline trigger so PSES triggers VSCE
• Ignore more bots
• Open draft PR