Use Java 17 as the LTS Version

[alzimmermsft]

Description

This PR updates the pipelines to use Java 17 instead of Java 11 as the LTS build version. There is a new parameter in ci.yml named JavaBuildVersion to allow libraries to continue using Java 11 as the LTS version while incompatibilities with Java 17 are resolved (such as using JDK internals that are no longer accessible through reflection or dependencies that don't support Java 17 such as PowerMock).

Most files changed in this PR are updates to Javadocs.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[alzimmermsft]

/azp run java - keyvault - data

[azure-pipelines]

Azure Pipelines failed to run 1 pipeline(s).

[alzimmermsft]

/azp run java - keyvault - data

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[alzimmermsft]

/azp run java - keyvault - data

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[alzimmermsft]

/azp run java - keyvault - data

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[alzimmermsft]

/azp run java - keyvault - data

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[alzimmermsft]

/azp run java - identity

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[check-enforcer]

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run java - [service] - ci

[kasobol-msft]

I'd keep one job with 11 or 9 (as long as core compiles partially with 9).

[mrm9084]

Some of these changes are incorrect for the Spring App Config library. And will need to deal with the latest version in review. #28701

[kasobol-msft]

lgtm.

[alzimmermsft]

/azp run java - spring - tests

[alzimmermsft]

/azp run java - storage - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[alzimmermsft]

/azp run java - cosmos - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[alzimmermsft]

/check-enforcer override

[alzimmermsft]

Live tests have been validated that their completion matches most recent runs without Java 17 in CI