FINERACT-2621: Upgrade to Spring Framework 7.x and Spring Boot 4.x

[SamaSVM]

Description

• Update Spring Boot 3.5.15 -> 4.0.7, Spring Framework 6.2.18 -> 7.0.8 and Spring Security 6.5.10 -> 7.0.6.
• Update JUnit 5.14.4 -> 6.0.3, EclipseLink 4.0.9 -> 5.0.1 and embedded Tomcat 10.1.55 -> 11.0.22.
• Update springdoc-openapi 2.8.17 -> 3.0.2 and spring-restdocs 3.0.5 -> 4.0.1;
  add resilience4j-spring-boot4 and spring-boot-starter-liquibase.
• Migrate Apache HttpComponents 4 (org.apache.http) to 5 (org.apache.hc.core5).
• Replace com.sun.mail/com.sun.activation with Eclipse Angus and commons-email2-jakarta;
  exclude com.sun.activation:jakarta.activation globally.
• Replace the hierynomus license Gradle plugin with a Spotless license header check.

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

• Write the commit message as per our guidelines
• Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
• Create/update unit or integration tests for verifying the changes made.
• Follow our coding conventions.
• Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
• This PR must not be a "code dump". Large changes can be made in a branch, with assistance. Ask for help on the developer mailing list.
• If merging this PR resolves a JIRA issue, I will mark that issue as resolved and set "Fix Version/s" appropriately.

Your assigned reviewer(s) will follow our guidelines for code reviews.

[Aman-Mittal]

@SamaSVM seems duplicate of effort #6069

[vidakovic]

@SamaSVM @Aman-Mittal it is a duplicate... I've left a comment in June here https://issues.apache.org/jira/browse/FINERACT-2621 and informed everyone that another volunteer took this over.

[vidakovic]

Also: this here Spring boot version 4.0.x vs Avinash's PR version 4.1.0!

[Aman-Mittal]

Moving this to draft now

[vidakovic]

Not sure what the intention with the draft is @Aman-Mittal. I think this is unfortunately not going to land upstream. A lot of file changes and work @SamaSVM, but I think it's best to close this one here.