fix(storage): add junit-vintage-engine to support native test discovery

[nidhiii-27]

When running native presubmit checks or building with the native profile, the builds for gapic-google-cloud-storage-v2 and google-cloud-storage-control fail with a SurefireBooterForkException. The specific error indicates that the TestEngine with ID junit-vintage failed to discover tests.

[ERROR] There was an error in the forked process
[ERROR] TestEngine with ID 'junit-vintage' failed to discover tests
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There was an error in the forked process
[ERROR] TestEngine with ID 'junit-vintage' failed to discover tests

This failure occurs because:

• The global native profile triggers the maven-surefire-plugin to perform test discovery using the modern JUnit 5 Platform Launcher
• The unit tests in these modules (e.g., StorageClientTest.java) are standard JUnit 4 tests
• The JUnit 5 launcher requires the junit-vintage-engine on the classpath to discover and execute these JUnit 4 tests

This PR fixes the discovery crash:

• Adds the junit-vintage-engine as a test-scope dependency in both gapic-google-cloud-storage-v2/pom.xml and google-cloud-storage-control/pom.xml
• Configures the maven-surefire-plugin within a local native profile to explicitly include the junit-vintage-engine dependency.

[gemini-code-assist]

Code Review

This pull request adds a 'native' profile to the pom.xml file for the gapic-google-cloud-storage-v2 module. This profile is configured to skip tests, with a note indicating that native testing for this specific module is handled within the google-cloud-storage module. I have no feedback to provide as there were no review comments.