Update version bump workflow

[vgrassia]

Type of change

- [ ] Bug fix
- [ ] New feature development
- [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [X] Build/deploy pipeline (DevOps)
- [ ] Other

Objective

This PR updates how we bump version numbers and cut the rc branch. The new procedure is outlined below.

If you have more than one project to cut rc for:

• Go to the DevOps repository and run the RC Branch Manager workflow with the following inputs.
  • cutmode.
  • Desired projects checked.
  • Version Number filled out.

You can also just run the Version Bump workflow in the repository by itself if you don't need to cut rc for multiple projects.

The following will take place:

• The version number is verified.
• The Version Bump workflow in the each repository is called via the GitHub CLI.
• The version will be bumped, committed to a branch, PR created, PR approved, PR merged.
• The Cut RC Branch workflow will run to create and push the rc branch.
• A Slack message will be sent to notify of the PR.

Code changes

• .github/workflows/_cut_rc.yml: Added to help cut the rc branch.
• .github/workflows/version-bump.yml: Removed workflow_call trigger as it's no longer needed. Added input for cutting the rc branch.

Before you submit

• Please check for formatting errors (dotnet format --verify-no-changes) (required)
• If making database changes - make sure you also update Entity Framework queries and/or migrations
• Please add unit tests where it makes sense to do so (encouraged but not required)
• If this change requires a documentation update - notify the documentation team
• If this change has particular deployment requirements - notify the DevOps team