RESTWS-1004: Upgrade to use Jakarta

[k4pran]

Description of what I changed

This PR upgrades the project to jakarta and to the latest OpenMRS core 3.x

Issue I worked on

see https://issues.openmrs.org/browse/RESTWS-1004

This is dependent on two other PRs that need merged first:

LegacyUI task - github.com/openmrs/openmrs-module-legacyui/pull/221
Core task - openmrs/openmrs-core#5523

Important changes

I tried as much as possible to avoid changing tests to avoid regression but it was unavoidable in some places so please scrutinize if these test changes could have any impact.

• In RestUtil class the change in setResponseStatus was due to deprecation and advised to use sendError for exceptions. See https://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpServletResponse.html#setStatus-int-java.lang.String. This however does mean it commits and sends the error rather than just setting a status, an alternative is we could instead set the status and add an error to the payload? I couldn't find any usages of this method across openmrs repos
• Removed FieldAnswerResource1_8 - Answers were removed from Field in core but please advise if we need to handle this another way.
• Changed some assertions in ClearDbCacheController2_0Test due to deprecation: https://docs.hibernate.org/orm/5.5/javadocs/org/hibernate/stat/Statistics.html#getSecondLevelCacheStatistics-java.lang.String-
• CommonsMultipartResolver has been removed, recommendation is to replace with org.springframework.web.multipart.support.StandardServletMultipartResolver. See https://github.com/spring-projects/spring-framework/wiki/Spring-Framework-6.0-Release-Notes however it doesn't seem to have an alternative for max size
• Add explicit jackson dependencies to match spring as classes were missing using existing dependencies
• Spring was complaining about duplicate uuid in path so renamed the parent one in FormResourceController1_9
• Bytebuddy dependency added for hibernate, no longer was being pulled in transitively
• Added an explicity name for ClobDatatypeStorageController create method, not sure why it was needed, but spring couldn't infer it after the upgrade.
• Spring no longer matches trailing slashes so this is removed where tests were failing - https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-3.0-Migration-Guide#spring-mvc-and-webflux-url-matching-changes
• The test PasswordResetController2_2Test > resetPassword_shouldResetUserPasswordIfActivationKeyIsCorrect was failing due to the recent changes in TRUNK-6435 limiting what can call methods to reset passwords. After speaking to @ibacher Instead what we do now is call setUserActivationKey which doesn't have the same check. The alternative would be to add to the allowed callers here - https://github.com/openmrs/openmrs-core/blob/471e1244286d71d1d4a171cebcb657c6a3a27e95/api/src/main/java/org/openmrs/api/db/hibernate/HibernateUserDAO.java#L643
• The test ChangePasswordController1_8Test > testUserChangeOtherUsersPasswordWithOutPrivilege was failing due to some changes inside spring that doesn't allow null locale in MessageSourceSupport. We pass null locales when throwing exceptions in AuthorizationAdvice so I added the default locale which fixed it. - TRUNK-6478 Populate null locales for Spring MessageSource openmrs-core#5523
• Updated taskSchedulerDataset.xml as there were mandatory fields missing and a change in field name - created_by to creator

Checklist: I completed these to help reviewers :)

• My IDE is configured to follow the code style of this project.

  No? Unsure? -> configure your IDE, format the code and add the changes with git add . && git commit --amend

• I have added tests to cover my changes. (If you refactored
  existing code that was well tested you do not have to add tests)

  No? -> write tests and add them to this commit git add . && git commit --amend

• I ran mvn clean package right before creating this pull request and
  added all formatting changes to my commit.

  No? -> execute above command

• All new and existing tests passed.

  No? -> figure out why and add the fix to your commit. It is your responsibility to make sure your code works.

• My pull request is based on the latest changes of the master branch.

  No? Unsure? -> execute command git pull --rebase upstream master

[dkayiwa]

@k4pran is this in draft simply because you are still working on the above build errors? 😊