KOGITO-6272 Ensure Quarkus extensions do not depend on quarkus-jackson

[evacchi]

While bumping to 2.5.0.CR1 a couple of jackson-related issues were
discovered

1. we were relying on quarkus-jackson being a dependency; but it was
   transitive from vertx; now vertx removed that dependency and we break
2. ObjectMapperGenerator is always generated even when resteasy is not
   present

• fix: add provided dependency to quarkus-jackson
• ObjectMapperGenerator should be optional (generate only with resteasy present)
• formatting

Many thanks for submitting your Pull Request ❤️!

Please make sure that your PR meets the following requirements:

• You have read the contributors guide
• Your code is properly formatted according to this configuration
• Pull Request title is properly formatted: KOGITO-XYZ Subject
• Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
• Pull Request contains link to the JIRA issue
• Pull Request contains link to any dependent or related Pull Request
• Pull Request contains description of the issue
• Pull Request does not include fixes for issues other than the main ticket

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.

build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

• Run all builds
  Please add comment: Jenkins retest this

• Run (or rerun) specific test(s)
  Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] tests

• Quarkus LTS checks
  Please add comment: Jenkins run LTS

• Run (or rerun) LTS specific test(s)
  Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] LTS

• Native checks
  Please add comment: Jenkins run native

• Run (or rerun) native specific test(s)
  Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] native

• Full Kogito testing (with cloud images and operator BDD testing)
  Please add comment: Jenkins run BDD
  This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

83.3% Coverage
0.0% Duplication

[rsynek]

Hi @evacchi, is there anything I can help with this PR?

[evacchi]

I ended up making quarkus-jackson a dependency here https://github.com/kiegroup/kogito-runtimes/pull/1731

[rsynek]

I ended up making quarkus-jackson a dependency here #1731

So it will get to OptaPlanner transitively as before? Ok.

[radtriste]

@evacchi anything new on that one ? should be merged ? (but conflict)

[evacchi]

I think it has been addressed as part of https://github.com/kiegroup/kogito-runtimes/pull/1731 @radtriste