✨ Add standard branch protection workflow

[Nicoretti]

Summary

Implement a final workflow that consolidates the results of other workflows to simplify branch protection and maintenance.

Details

Currently, our branch protection is based on individual test workflows which makes it cumbersome to maintain, especially when new Python versions are supported or old ones are deprecated. Each time a change occurs, the branch protection rules need to be updated to reference specific matrix build names. By implementing a final workflow that checks the success of other workflows, we can simplify the branch protection setup and its maintenance.

Background & Context

The motivation for this feature is to streamline the branch protection rules. This will significantly reduce the effort required to keep the rules up to date with the changes in supported or deprecated Python versions. Instead of updating references for each individual matrix build, a single final workflow can be referenced in the branch protection rules. This will simplify the configuration and automate the setup process across different projects, even if the workflow inputs differ.

Examples

• A final workflow job named approval-gate that aggregates the status of all necessary workflows and can be referenced in branch protection rules.

References

• ✨ Build matrix configuration on workflow call #30
• https://github.com/exasol/project-keeper/blob/main/project-keeper/src/main/resources/templates/.github/workflows/ci-build-db-version-matrix.yml