Chore: the native image should be tested in github actions

[murdos]

In the past I added the startup of the native image in b936139 but as demonstrated by #9861 this is not enough

I think we need one or two E2E tests (one for maven, and one for gradle) that generates an application, and check that there's no 500 errors.
Theses E2E could then be ran in the build_native_docker_image github action, in order to test the native image.

An alternative could be to reuse ci-tests/generate.sh in build_native_docker_image

[renanfranca]

An alternative could be to reuse ci-tests/generate.sh in build_native_docker_image

Do you know if the following issue is related?

• Native testing support #5561

[atomfrede]

No I would say. The linked issue is about using the existing unit and integration tests with native profile. There has been an issue with mockito if i remember correctly.
This issue should start the native image and add some modules. Maybe we can use our testsuite to do that but doing the minimal thing in ci might be enough