Reduce redundancy between JVM Tests and Native Tests GitHub Workflows

[apupier]

Is your feature request related to a problem? Please describe.

To be confirmed but it seems that the Native tests GitHub workflow job is also playing the JVM tests, like the JVM Test job.

Describe the solution you'd like

• a single GitHub Workflow job for JVM and Native tests

it would allows to spin less Machines, to not recompile java classes and to avoid playing JVM tests (launched with maven-surefire-plugin) 2 times

Describe alternatives you've considered

do not play Mave-surefire-plugin tests with profile native but it remains 2 different machines and to recompile Java classes. The advantage is that we can still running with different JDK. Not using the GraalVM for JVM tests sounds a good thing, closer to end-user usage.

Additional context Add any other context or screenshots about the feature request here. Wondering if the "Build" job is not mereley redundant too https://github.com/KaotoIO/kaoto-backend/blob/ec08514cbcb279d86062e8ec3bbf4e9736adb42b/.github/workflows/analysis.yml#L12

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This has been closed due to inactivity. If you want to further pursue this development, please reopen it again adding the new information.