Consider grouping Google related integration tests

Much like we have grouped AWS and Azure (see https://github.com/apache/camel-quarkus/pull/2477 ) related tests, thus saving some CI time, we should consider doing the same for Google. Whether it makes sense to group all Google tests depends on how much their dependency sets overlap. This can be done after https://github.com/apache/camel-quarkus/pull/2505

After PR #2505, inspect how AWS and Azure integration tests were grouped in PR #2477. Compare the dependency sets of the Google tests, then group them where overlap supports it and verify that CI time improves without breaking the integration test coverage.

Written by the indexing model from the issue text.