CAMEL-22857 Convert camel to Jackson 3 - use jackson 3 in all camel components, use camel-jackson3 over camel-jackson

[cunningt]

Description

• convert camel to Jackson 3 (com.fasterxml.jackson -> tools.jackson, API changes)
• all components that used camel-jackson now use camel-jackson3
• import the tools.jackson:jackson-bom instead of the com.fasterxml.jackson:jackson bom in parent/pom.xml
• update ObjectMapper references for immutability changes
• drop wizard metrics upgraded to 4.2.38 to support Jackson 3
• networknt-json-schema-validator upgrade from 1.5.9 -> 3.0.0 along with API changes (in order to support Jackson 3) -
• jsonschema-generator upgrade to 5.0.0
• flowable upgrade to 8.0.0 (in order to support Jackson 3)
• jackson-annotations does not change groupId/package (jackson 2 annotations supports both Jackson 2 and Jackson 3, introduced a property for jackson2-annotations-version)

There are five components that cannot upgrade to Jackson 3. They are still using Jackson 2 but since Jackson 2 and Jackson 3 maintain different package names there do not seem to be any issues with them staying on Jackson 2 temporarily

• camel-openapi (open PR for Jackson 3 support for swagger, will upgrade it to Jackson 3 when PR is merged and released)
• camel-opensearch (open PR for Jackson 3 support for opensearch, will upgrade it when PR is merged and released)
• camel-jslt (open PR for Jackson 3 support for jslt, will upgrade it when PR is merged and released)
• camel-json-patch (Jackson 3 not supported yet, project seems abandoned, camel-json-patch deprecated, will not try to upgrade before removal)
• camel-torchserve (Jackson 3 not supported yet, camel-torchserve is deprecated, will not try to upgrade before removal)

Target

• I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Tracking

• If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• [x ] I checked that each commit in the pull request has a meaningful subject line and body.

• [x ] I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.