[Java] [Native] Unify exception messages for async, add the status code

[Gama11]

The template has two methods for creating API exceptions, and the enhancements from #9169 didn't make it to the async version.

• unify the signatures of the two methods (name, arguments)
• make sure the sync version is not generated with asyncNative
• extract the formatting logic into a common formatExceptionMessage() method
• add the status code to the exception message as well, not just the body
• shortened "call received non-success response" to a more concise "call failed with"

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package 
  ./bin/generate-samples.sh
  ./bin/utils/export_docs_generators.sh
  

  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  For Windows users, please run the script in Git BASH.
• File the PR against the correct branch: master, 5.1.x, 6.0.x
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

[Gama11]

The AppVeyor failure seems unrelated / master is also failing.

[wing328]

cc @MosheElisha (author of #9169)

@bbdouglas (2017/07) @sreeshas (2017/08) @jfiala (2017/08) @lukoyanov (2017/09) @cbornet (2017/09) @jeff9finger (2018/01) @karismann (2019/03) @Zomzog (2019/04) @lwlee2608 (2019/10) @nmuesch (2021/01)

[MosheElisha]

LGTM. Thanks.