feat: separate native-image-shared-config into its own module

[mpeddada1]

• This PR separates out the native image configurations into their own artifact called native-image-shared-config. A pom.xml file focused on native image is easier to maintain.
• The native-image-shared-config artifact is brought in as a parent of java-shared-config
• Testing locally with google-http-java-client by adding the following and running mvn test -Pnative -Pnative-deps -Dtest=*Test:

 <parent>
    <groupId>com.google.cloud</groupId>
    <artifactId>native-image-shared-config</artifactId>
    <version>1.6.2-SNAPSHOT</version>
  </parent>

[meltsufin]

I think you need to move this section to the new root parent native-image-shared-config, and it doesn't need to be duplicated here as it will be inherited.

[mpeddada1]

Good point, done. Moved this content from java-shared-config/pom.xml to native-image-shared-config/pom.xml and removed the duplicated content.

[suztomo]

Once you merge this "feat" pull request, check Release Please pull request has correct updates for the versions.

[mpeddada1]

Thank you @suztomo! Also the stage job ran successfully with this PR:

INFO] --- maven-deploy-plugin:3.1.1:deploy (default-deploy) @ google-cloud-shared-config-parent ---
[INFO] Skipping artifact deployment
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Native Image Shared Config 1.6.2-SNAPSHOT .......... SUCCESS [01:41 min]
[INFO] Google Cloud Shared Config 1.6.2-SNAPSHOT .......... SUCCESS [02:36 min]
[INFO] google-cloud-shared-config-parent 0.1.0-SNAPSHOT ... SUCCESS [  0.910 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  05:33 min
[INFO] Finished at: 2023-11-28T16:01:50Z
[INFO] ------------------------------------------------------------------------
Finished uploading the staging repository

[mpeddada1]

The failure of job labelled kokoro is due to a failure in the publish_javadoc job which shows:

cp: cannot create regular file 'target/docfx-yml/history.md': No such file or directory

It appears that this job has experienced this issue since the last couple of releases:

[burkedavison]

I'm surprised that publish_javadoc11.sh is involved with this repo since we aren't publishing documentation anywhere. It might be that this job is unnecessary.

[alicejli]

I'm surprised that publish_javadoc11.sh is involved with this repo since we aren't publishing documentation anywhere. It might be that this job is unnecessary.

Piping in here - pretty sure all the Kokoro release jobs in this repo are obsolete as they were migrated to g3. See cl/533291527