Skip surefire when building the IntegrationKit

[lburgazzoli]

What happened?

When building an IntegrationKit, the maven-surefire-plugin:test, maven-resources-plugin:testResources mojos are useless and can be skipped to save some time and CPU cycles.

Steps to reproduce

1. run an integration
2. watch the maven build log

Relevant log output

{"level":"info","ts":"2024-05-07T21:55:54Z","logger":"camel-k.maven.build","msg":"--- maven-surefire-plugin:2.12.4:test (default-test) @ camel-k-integration ---"}
{"level":"info","ts":"2024-05-07T21:55:57Z","logger":"camel-k.maven.build","msg":"No tests to run."}
{"level":"info","ts":"2024-05-07T21:55:57Z","logger":"camel-k.maven.build","msg":""}

{"level":"info","ts":"2024-05-07T22:01:01Z","logger":"camel-k.maven.build","msg":"--- maven-resources-plugin:2.6:testResources (default-testResources) @ camel-k-integration ---"}
{"level":"info","ts":"2024-05-07T22:01:01Z","logger":"camel-k.maven.build","msg":"Using 'UTF-8' encoding to copy filtered resources."}
{"level":"info","ts":"2024-05-07T22:01:01Z","logger":"camel-k.maven.build","msg":"skip non existing resourceDirectory /tmp/kit-cota5gcjp6es73cbksm0-170601170/maven/src/test/resources"}

Camel K version

No response

[squakez]

@lburgazzoli fyi, we're using area/build-system for those issues related to the operator build image (ie, make images). We're instead using area/builder for the other one. It can be misleading and I'm moving the first to area/build-operator.