Skip deploying of java 17 subprojects

[JonasKunz]

What does this PR do?

During the last release I noticed that our release job attempts to deploy the new java 17-specific subprojects aswell, which is not intentional to my knowledge.

[eyalkoren]

Ahh, because it is a top level subproject we need to say that explicitly?
LGTM

[apmmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-01-31T14:48:07.717+0000

• Duration: 56 min 24 sec

Test stats 🧪

Test	Results
Failed	0
Passed	3446
Skipped	43
Total	3489

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run benchmark tests : Run the benchmark tests.

• run jdk compatibility tests : Run the JDK Compatibility tests.

• run integration tests : Run the Agent Integration tests.

• run end-to-end tests : Run the APM-ITs.

• run windows tests : Build & tests on windows.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[JonasKunz]

Ahh, because it is a top level subproject we need to say that explicitly? LGTM

Exactly. The plugin projects for example do not need to specify it because they inherit the settings from their apm-agent-plugins (potentially transitive) parent, where the maven-deploy-plugin.skip is set to true.