Issue #2777 - jackson-databind update from 2.21.1 to 2.22.0

[01es]

Resolve #2777

To be completed by the pull request creator

This section should be completed with reference to section Preparing PR of the Code and PR reviews wiki page.

• Create the pull request as a draft by tapping the dropdown arrow on the 'Create pull request' button under the pull request description (below the text box where this description is being edited) and changing the default Create pull request to Draft pull request.
  Or, if the pull request has already been created, convert it to draft by tapping the "Convert to draft" link beneath the "Reviewers" section.

• A self-review of all changes has been completed, and the changes are in sync with the issue requirements.

• Changes to the requirements have been reflected in the issue description.

• Any "leftovers" such as sysouts, printing of stack traces, and any other "temporary" code, have been removed.

• Minor refactorings, such as renamings, extraction of constants, etc., have been addressed.

• All existing and new Java tests pass successfully by running them with Maven.

• All existing and new Web tests pass successfully.

• The correct base branch has been selected for these changes to be merged into.

• The latest changes from the base branch have already been merged into this feature branch (and tested).

• Added a change overview to the issue description or as a wiki page, referenced in the issue description.
  Some issues might be very descriptive and serve in place of a wiki page.
  In such cases consider adding label Wiki like to the issue.

• This pull request does not contain significant changes, and at least one appropriate reviewer has been selected.

• The pull request has been made ready for review by tapping the "Ready for review" button below the list of commits on the pull request page.

To be completed by the pull request reviewer

This section should be completed with reference to section Performing PR review of the Code and PR reviews wiki page.

• The In progress label has been added to the pull request in GitHub.

• The issue requirements have been read and understood (along with any relevant emails and/or Slack messages).

• The correct base branch is specified, and that base branch is up-to-date in the local source.

• The issue branch has been checked out locally, and had the base branch merged into it.

• All automated tests pass successfully.

• Ensure the implementation satisfies the functional requirements.

• Ensure that code changes are secure and align with the established coding practices, including code formatting and naming conventions.

• Ensure that code changes are documented and covered with automated tests as applicable.

• Ensure that code changes are well-suited for informal reasoning.

• Ensure that changes are documented for the end-user (a software engineer in the case of TG, or an application user in the case of TG-based applications).

• If there are significant changes (described above), special attention has been paid to them.
  Marked the task items in section "Significant changes" as completed to indicate that corresponding changes have been reviewed, improved if necessary, and approved.

• The issue or issues addressed by the pull request are associated with the relevant release milestone.

To be completed by the pull request reviewer once the changes have been reviewed and accepted

• The changes have been merged into the base branch (unless there is a specific request not to do so, e.g., they are to be released to SIT).

• The issue branch has been deleted (unless the changes have not been merged - see above, or there is a specific request not to do so).

• The In progress label has been removed from the pull request.

• The Pull request label has been removed from the issue.