Simplify Apicurio Registry upstream testing strategy

[carlesarnal]

Summary

This PR simplifies and optimizes the Apicurio Registry CI/CD pipeline by restructuring the verification workflows into a modular, parallel architecture.

Changes

• Modular workflow structure: Replaced monolithic workflows with verify.yaml orchestrating specialized sub-workflows (verify-build.yaml, verify-unit-tests.yaml, verify-integration-tests.yaml, etc.)
• Parallel test execution: Integration tests now run as 11 parallel matrix jobs (3 storages × 3 profiles + 2 extras) instead of sequential execution
• Reusable workflows: Added reusable-build.yaml, reusable-docker-build.yaml, and reusable-notify-slack.yaml to eliminate code duplication
• Optimized builds: Unit tests run in parallel using Surefire forks against pre-built artifacts
• Updated action versions: All GitHub Actions updated to v4/v5

Test plan

• Verify all workflow phases execute correctly
• Confirm integration test matrix runs in parallel
• Validate Docker image publishing on main branch pushes
• Check Slack notifications trigger appropriately

[jsenko]

This does not need to be committed?

[carlesarnal]

No, but if you read it, you'll get a much better idea of what's going on. I'm going to update the PR description with this.

[jsenko]

This is pretty big. I trust you if this works, is there anything in particular that you want opinion on?

[carlesarnal]

This is pretty big. I trust you if this works, is there anything in particular that you want opinion on?

About the approach itself. I'm not asking for a full review of the thing :)

The TLDR is essentially the following:

• Lint and validate. db lint, docs verification.
• Build: build java backend, ui, publish temporary docker images and make maven artifacts available to the rest of the jobs
• Unit tests: the obvious, mvn verify against the already build artifacts. No re-building of the maven modules.
• Integration tests: the same workflows as before, running in a matrix, so we can run them in parallel.
• Extra tests: tests ui, legacy v2, typescript sdk integration, examples
• sdk verification: python sdk, go sdk
• native build: building native executable and running integration tests

[EricWittmann]

I approve in principal. :) Happy to have it merged and we can see how it goes and fix/iterate if needed.

[jsenko]

I'm a big fan of reusable workflows and matrix execution.... I want to do that in apicurio-testing as well. So thumbs up from me! We definitely accumulated some unnecessary complexity over time.

Additional note: I don't see any changes to the operator workflows, correct? Because they aren't going to run in this PR unless there's a change in the operator dir.

[carlesarnal]

I'm a big fan of reusable workflows and matrix execution.... I want to do that in apicurio-testing as well. So thumbs up from me! We definitely accumulated some unnecessary complexity over time.

Additional note: I don't see any changes to the operator workflows, correct? Because they aren't going to run in this PR unless there's a change in the operator dir.

Correct, this is simplifying the workflows and remove some unused ones, like the RHBOQ one. Regarding the operators, the only change is to re-use the slack notification one, that was replicated across the different ones, and one it's simplifies into a single, parametrized one.

[carlesarnal]

All the workflows are green. I'm merging this and we can continue iterating on it. This is the first round to improve our processes. I'm also trying to improve the speed, ~30min is way too much.