Improve release workflow: true/false input for VS Code release to pull in Language Services + make all local NPM steps into reusable script/steps

[KetchupOnMyKetchup]

As part of research from #107 we are reducing the manual steps in our release workflow.

Our current release workflow is documented here: https://github.com/github/workflow-development/blob/main/docs/vscode/release-new-version.md

Our current ideal scenario for release is:

1. Go to Language Services and select "major" or "minor" or "patch" and it will pull in the previous version and increment for you based on your selection. A PR will be opened, you approve it and the release is completed. The release and release notes will be autogenerated.
2. Go to the VS Code repo and select "major" or "minor" or "patch" and it will pull in the previous version and increment for you based on your selection. You will also be asked "true/false" to pull in Language Services or not. This workflow will automatically create a release PR, incrementing the VS Code and Language Services version by running the NPM steps as a script (if true was selected to pull in Language Services).

This issue is 1 part of 4 for the release improvement.

• 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

Tasks for this issue:

• Make all local NPM steps for the VS Code Repo to update Language Services a script that updates it within the workflow as part of the same PR that is created with the updated release version for the VS Code extension. See example of PR below:
  
• When kicking off a Workflow for Release, ask if "Would you like to get the latest version of Language Services" and accept true/false
• Update documentation with all changes https://github.com/github/workflow-development/blob/main/docs/vscode/release-new-version.md

[lrotschy]

This issue covers Local changes to bump verison and edit Changelog steps from https://github.com/github/workflow-development/blob/main/docs/vscode/release-new-version.md#vs-code-repo

[felipesu19]

Hey, fun fact, you only pull a new version of language service... if there is a new version to pull, which means we can't really test this until we cut a new release of language service. I'm going to put the pr on hold until we're ready to drive a new release and we can test that this is working then.

(See below comment)

[felipesu19]

Ok, we were able to test this by committing a change to package-lock.json that modified language-server to an older version, the automation when run via workflow dispatch picked up the newest version. That bit is working!

#145