chore(engine): bump spring dependency to version 6

[joaquinfelici]

Related to #4869

Duplicate of #4862 (reverted) created for CI fixes

[joaquinfelici]

Hints for review

The spring 6 upgrade hasn't changed since the original reverted PR. All new changes are related to CI or QA modules.

CI / QA

• Spring 6 is no longer compatible with Java 11.
• When we can, we're now building with Java 17 by default.
• Some jobs still need to use Java 11. In these cases, we're either not executing spring 6 code or we override the Spring version to keep using Spring 5 (for example jdk11 or instance migration jobs).
• When using JDK 17, some modules needed to be opened as they are no longer by default.

[yanavasileva]

❌ Many of the QA DB tests stages are not run by default in the PR even with labels. I expect failures for migration, large, since the JDK 11 there.

📓 General note, as long as we have JDK 11 daily stages, we are fine to move most of the stages to JDK 17. But for some it make sense to leave them with JDK 11 - instance-migration, old-engine, rolling-update as they test specific scenarios that are not covered with JDK 11 daily stages.

✍️ Let's extend the upgrade guide that to mention that Spring 6 doesn't support JDK 11 and users need to override the spring 6 dependency to with spring 5 to stay if they use JDK11.

[joaquinfelici]

@yanavasileva

• I added a java11 profile in the qa module to override the spring version for every build with java11.
• I extended the documentation here.
• Pipelines are still running 🕐

[yanavasileva]

👍 Looks good. Only small improvement in the stage-types.

daily stages run on mysql here: #4965

[joaquinfelici]

Main pipeline is failing due to flakiness in test BuiltinExceptionCodeForeignKeyConstraintViolationTest, all other tests and stages are green.