MI-207: Manual release pipeline with input

[kai-nguyen-aligent]

Description of the proposed changes

• Switch to manual triggered release pipeline & remove version plan check from pull request. This fix 2 problems that we have at the moment:
  1. Pull Request pipeline failed in situations where we want to merge to main but do not want to release new versions. Eg: pipeline changes, update devDependencies, etc.
  2. Support pipeline input options. Eg: --first-release is needed when we add new package which isn't published yet. We haven't been unable to release @aligent/nx-openapi@1.0.0 & @aligent/nx-serverless@1.0.0 packages yet for this reason.
• Configure Nx release so CHANGELOG.md and Github release are generated automatically when there is a release.
• Added name for some pipeline steps for clarity.

Other solutions considered (if any)

• I choose to use manual triggered release instead of using job control condition in release pipeline as it's easier to implement & we have more control over the pipeline inputs.

Notes to PR author

⚠️ Please make sure the changes adhere to the guidelines mentioned in the Aligent Contribution Guide

Notes to reviewers

🛈 When you've finished leaving feedback, please add a final comment to the PR tagging the author, letting them know that you have finished leaving feedback