chore: Bump version to the next release version 2.8.0

[anandf]

Minor change to bump the version number in master branch to the next release.
Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• Optional. My organization is added to USERS.md.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.

Please see Contribution FAQs if you have questions about your pull-request.

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: -0.01 ⚠️

Comparison is base (03513eb) 49.06% compared to head (b276c5d) 49.06%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #13368      +/-   ##
==========================================
- Coverage   49.06%   49.06%   -0.01%     
==========================================
  Files         248      248              
  Lines       42816    42816              
==========================================
- Hits        21009    21006       -3     
- Misses      19688    19690       +2     
- Partials     2119     2120       +1     

see 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[drpaneas]

Shouldn't this be automated by a bot or something? Also there are multiple ways to embed the version nowadays into the build without the need of the VERSION file. https://developers.redhat.com/articles/2022/11/14/3-ways-embed-commit-hash-go-programs

[34fathombelow]

Lgtm, thanks! This is actually automated now in our new release process.

[jannfis]

LGTM!