Bump oc10 version to 10.8.1 for development

[phil-davis]

Description

We are getting some new tests added that are only applicable to code that is currently in master. The new tests are not relevant to version 10.8.0. We need some way for the test runner to understand that we are moving forward from 10.8.0.

This PR bumps the version in master to "10.8.1 prealpha" for development purposes.

Note: the actual next release might be 10.9.0 - we are not deciding that here. This bump is just making the minimal bump for development.

Note: this replaces #39048 which suggested bumping now to "10.9.0 prealpha"

How Has This Been Tested?

CI

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Database schema changes (next release will require increase of minor version instead of patch)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:
• Changelog item, see TEMPLATE

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[phil-davis]

@micbar we are getting more new/changed test scenarios in master since 10.8.0 that are for feature/behavior changes since 10.8.0. They are tagged @skipOnOcV10.8.0 because they cannot pass on a real 10.8.0 system.

But core master still thinks it is 10.8.0. So those scenarios are not currently running in CI of PRs to master. That is not good.

This PR gives master the "knowledge" that it is later software than 10.8.0. Please review. Can we merge it?