Improve the release workflow research spike

[KetchupOnMyKetchup]

Research:

• Is there an open sourced good way to release packages? Feel free to put any research notes in the discussion!
• Check other internal VS Code extensions like Primer / Copilot / etc
• Look for standardized steps
• Check in slack?

We want an option to:

1. release VS Code only without language services option
2. release VS Code with language services option

We could definitely remove the need to download locally and setup a script to do npm install / npm i for the local part

^ We do want to fix before GA.

The goal of this issue is to have a plan for making our release better and to create separate issues for implementation. Those separate issues should include the task of documenting any changes to our release doc https://github.com/github/workflow-development/blob/main/docs/vscode/release-new-version.md

[KetchupOnMyKetchup]

Will create separate issues for:

1. Have a true/false input on VS Code release to pull in language services. Make local NPM steps into reusable script/steps within Workflow.
2. Auto-increment version for both VS Code and Language Services based on input of "major", "minor", or "patch" release.
3. Generate release notes as an automatic workflow step
4. Today, we update every package in the language services together, but ultimately we should have the ability to release individual packages.

[KetchupOnMyKetchup]

Created 4 issues:

• Improve release workflow: Setup ability to release individual packages of Language Service #132
• Improve release workflow: Generate release notes as an automatic workflow step #131
• Improve release workflow: Auto-increment version for both VS Code and Language Services based on input of "major" or "minor" or "patch" release #130
• Improve release workflow: true/false input for VS Code release to pull in Language Services + make all local NPM steps into reusable script/steps #129