Switch to Spring Boot 3 and Java 17

[sbegaudeau]

This change will only be performed after the general availability of Spring Boot 3 (we won't move to a milestone). We may not switch to the release 3.0.0 just after its release and we may wait for a 3.0.x or even a 3.1.x release. This issue is just here to start discussing this migration and the changes required by this new version.

See https://spring.io/blog/2022/05/24/preparing-for-spring-boot-3-0

[sbegaudeau]

Among the changes which may impact us :

• Switch from javax.xxx dependencies to jakarta.xxx for example import javax.servlet to import jakarta.servlet
• Potential switch to PathPatternParser from the AntPatternParser (not strictly required but encouraged)

[sbegaudeau]

See https://github.com/spring-projects/spring-boot/releases/tag/v3.0.0

[sbegaudeau]

Things to consider:

• Spring Security 5.8 to prepare the migration to Spring Security 6.0.0 here
• Migration to Spring security 6.0 here
• Spring Data 2022.0 release notes here

We will have to keep in mind that:

• Methods like authorizeRequests and antMatchers have been deprecated in Spring Security 5.8 and removed in 6.0 and this will have some impact on our security configuration. By switching from Spring Boot 2.7.x to Spring Boot 3.X, we will directly move from Spring Security 5.7.x to Spring Security 6.x and thus encounter the API breaks in question.
• We are extending PagingAndSortingRepository in multiple interfaces in sirius-web-persistence and this interface will now longer extend CrudRepository so any piece of code using things like IProjectRepository or IDocumentRepository would stop having access to methods such as findById, delete, save. To restore this behavior, our various repositories will have to switch to extends PagingAndSortingRepository<XXX, YYY>, ListCrudRepository<XXX, YYY>.

We may also encounter some changes in websocket support or method security, but I haven't evaluated those parts yet.