chore: add secret manager module and sample it tests to native image CI

[zhumin8]

Changes in this pr:

• Add secret manager sample app test to native test ci. Tests run for sample application:

com.example.SecretManagerSampleIntegrationTests > testDeleteSecret() SUCCESSFUL

com.example.SecretManagerSampleIntegrationTests > testCreateReadSecret() SUCCESSFUL

com.example.SecretManagerSampleIntegrationTests > testApplicationStartup() SUCCESSFUL

• Add secret manager module it test to native test ci.
  tests run for module:

com.google.cloud.spring.secretmanager.it.SecretManagerTemplateIntegrationTests > testReadWriteSecrets() SUCCESSFUL

com.google.cloud.spring.secretmanager.it.SecretManagerTemplateIntegrationTests > testUpdateSecrets() SUCCESSFUL

com.google.cloud.spring.secretmanager.it.SecretManagerTemplateIntegrationTests > testReadMissingSecret() SUCCESSFUL

• Test resource uniqueness for parallel runs :
  • Module test: add uuid to secret used.
  • Sample test: refactor into 2 separate tests.
    • SecretManagerSampleLoadSecretsIntegrationTests tests for sample application load, which load secrets as properties into the application context; This test uses one pre-created secret in ci, read-only.
    • SecretManagerSampleTemplateIntegrationTests tests for SecretManagerTemplate operations in sample application. This test now creates and deletes unique secrets for each run.

[diegomarquezp]

didn't intend to review - I mistakenly went over this one when approving deps PRs :)

[mpeddada1]

@zhumin8 Apologies for the additional work! We recently merged the PR to set up sub-jobs for native image checks so as a extra step, we need to add secretmanager-sample here for it to be included in the CI.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication