fix(java): include integration tests for native image testing

[mpeddada1]

Some background:
We want to run integration tests and unit tests (ending in *ClientTest) with the native profile. For this purpose, we want to ignore any exclusions that take place in other maven-surefire-plugin configurations within the java-shared-config pom or other child poms so that we can explicitly include these tests. However, using excludedGroups in java-spanner-jdbc causes the overriding of the exclusion to be ignored. This results in integration tests being skipped in native mode which leads to native-image testing to fail with the message: Test configuration file wasn't found. Make sure that test execution wasn't skipped.

This change replaces the use of excludedGroups with exclude, which allows the the maven-surefire-plugin configuration for the native profile to take precedence when mvn test -P native is called. Manual testing with mvn test results in only unit tests being run, therefore showing no change in current behavior for standard Java.

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes #719 ☕️

[suztomo]

https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#excludedGroups

(TestNG/JUnit47 provider with JUnit4.8+ only and JUnit5+ provider since 2.22.0) Excluded groups/categories/tags. Any methods/classes/etc with one of the groups/categories/tags specified in this list will specifically not be run.

Was that wrong usage of excludedGroups before this PR?

[mpeddada1]

Ideally, we want to run integration tests and unit tests (ending in *ClientTest) with the native profile. For this purpose, we tend to ignore any exclusions that take place in other maven-surefire-plugin configurations within the java-shared-config pom or other child poms: https://github.com/googleapis/java-shared-config/blob/ac44ba11d2da2f649670867c520f90253a8a41ff/pom.xml#L807, so that we can explicitly include these tests. However, with the use of excludedGroups in java-spanner-jdbc, this overriding of the exclusions gets ignored, therefore causing no integration tests to run in native mode. Changing this to exclude fixes this issue.

[suztomo]

Was that wrong usage of excludedGroups before this PR?

it seems correct usage to skip the integration test marked with @Category(ParallelIntegrationTest.class) in this repository.

@mpeddada1 With this change in this PR, does mvn test skip the tests marked with @Category(ParallelIntegrationTest.class), such as ITJdbcSimpleStatementsTest and ITJdbcReadOnlyTest?

[mpeddada1]

Good question. Just ran mvn test with this change and can confirm that tests annotated with @Category(ParallelIntegrationTest.class) are skipped. Only unit tests are executed.

[suztomo]

Thank you for confirmation.

[mpeddada1]

Thank you for the review @Neenu1995 and @suztomo!