[Java][Jersey2] Make generated client code thread safe

[tsiq-karold]

PR checklist

• Read the contribution guidelines.
• Ran the shell script under ./bin/ to update Petstore sample so that CIs can verify the change. (For instance, only need to run ./bin/{LANG}-petstore.sh and ./bin/security/{LANG}-petstore.sh if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in .\bin\windows\.
• Filed the PR against the correct branch: 3.0.0 branch for changes related to OpenAPI spec 3.0. Default: master.
• Copied the technical committee to review the pull request if your PR is targeting a particular programming language.

Description of the PR

This PR is to make the generated Jersey 2 client thread safe. Currently, the only way to get to response headers and status is by inspecting some fields on the ApiClient which is not thread safe. This PR changes the generated code to follow a similar pattern used by other generated clients with "withHttpInfo" flavours of each method. It is backwards compatibility breaking as it removes the existing header and status fields.

Fixes #7453

cc @bbdouglas @JFCote @sreeshas @jfiala @lukoyanov @cbornet @jeff9finger

[jeff9finger]

approved

[jeff9finger]

LGTM

[wing328]

@tsiq-karold thanks for the PR. Sorry for the delay in merging this PR into master due to Chinese New Year celebration.

@jeff9finger thanks for reviewing the change.

[wing328]

Upgrade Note

The following properties have been removed from ApiClient.java:

-  protected int statusCode;
-  protected Map<String, List<String>> responseHeaders;

To obtain the status code and HTTP headers, please use the additional WithHttpInfo methods instead.