BRE-40 Add step to report upcoming release version to Slack

[urbinaalex17]

Type of change

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

Objective

Report upcoming release to Slack using the generate version bump by the workflow.

Related PR: bitwarden/gh-actions#281

Code changes

• .github/workflows/version-bump.yml: Add step to report upcoming release

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 28.13%. Comparing base (5075d08) to head (80049a8).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9201      +/-   ##
==========================================
+ Coverage   28.12%   28.13%   +0.01%     
==========================================
  Files        2362     2362              
  Lines       69880    69880              
  Branches    13141    13141              
==========================================
+ Hits        19654    19661       +7     
+ Misses      48668    48661       -7     
  Partials     1558     1558              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

Checkmarx One – Scan Summary & Details – 1897be24-6522-458c-8c00-0e9ffaf41ed1

New Issues

Severity	Issue	Source File / Package	Checkmarx Insight
	Missing_HSTS_Header	/libs/common/src/services/api.service.ts: 222	Attack Vector
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 465	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 457	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 481	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 473	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...