Am 702

[leleueri]

Fix AM-702

Description

This PR upgrade AM to use the latest gravitee-bom & gravitee-parent.
It is by extension the migration to Spring 6.

This PR is split in different commit, to track the different changes made along the issues we meet during this migration.

Main impacts / changes:

• Now AM is compiled using Java 17
• Spring & vertx upgrade
• Upgrade of spring data & R2DBC
• Now R2DB driver must be compatible with the R2DBC-SPI 1.0
• The default connection pool settings for R2DBC have been changed

How to test

please run the full non regression pack on nightly env (Mongo & JDBC one)

Documentation inputs

⚠️ This PR will introduce a Breaking change for AM 4.1 and need to be highlighted properly.

• First starting from this PR, AM 4.1 will required Java 17 as runtime
• The version of the R2DBC drivers must be compatible with the R2DBC-SPI 1.0 (basically, the driver version must start with 1.x see below ⬇️ )
• The default values for RDMS connection pool have change as with the latest version of R2DBC a timeout set to 0 doesn't mean infinite anymore, we take this opportunity to change the default timeout values but also some connection pool size values. Here is the new values:

    initialSize: 1
    maxSize: 50
    maxIdleTime: 30000
    maxLifeTime: -1
    maxAcquireTime: 3000
    maxCreateConnectionTime: 5000

For information, previous values were:

    initialSize: 0
    maxSize: 10
    maxIdleTime: 30000
    maxLifeTime: 0 # not valid anymore with R2BC 1.x
    maxAcquireTime: 0 # not valid anymore with R2BC 1.x
    maxCreateConnectionTime: 0 # not valid anymore with R2BC 1.x

Here is the versions we used for the R2DBC drivers
postgresql : 1.0.2.RELEASE
mariadb: 1.1.2
mysql: 1.0.2
mssql : 1.0.0.RELEASE

WARNING ⚠️ DO NOT use the 1.0.2.RELEASE for mssql / SQLServer as this version seems to be buggy (see r2dbc/r2dbc-mssql#276)

Note: could be nice to have the new default settings and the R2DBC driver version in the Repository page

[mariano-fernandez]

I just finished commit 4 so far 😅
I'll pick up from there later

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
5 Code Smells

2.8% Coverage
0.5% Duplication

The version of Java (11.0.17) you have used to run this analysis is deprecated and we will stop accepting it soon. Please update to at least Java 17.
Read more here

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[mariano-fernandez]

I stopped half way. It's hard to review this upgrades. Since there aren't any functional improvements, in my opinion if the CI is green, we can merge.

There will be a full regression pack to make sure that we didn't miss anything else.