[java][microprofile] update dependency to newer version

[wing328]

• update dependency to newer version 1.4.1
• better indentation

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.3.0), 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.

cc @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)

[mzellho]

Hi @wing328,

two more minor things that would be cool if they could be part of 5.3.1:

1. I think it would be good if the cxf version was constant, so pom.mustache#L108 should be changed, so it uses ${cxf-version} (maybe other dependencies could use properties holding their respective versions as well?)
2. we're using dependency tracker to keep an eye on our applications' security vulnerabilities, and it seems like cxf-core should be updated to something >= 3.3.4

What do you think?

BR,
Max

[wing328]

Please feel free to submit a PR to update other dependencies to newer versions.

I only did it for microprofile so as to fix the CI failure.