Fix Conditions for Spring Boot 2.4 to 2.5 Upgrade recipes

[fabapp2]

Thanks for reporting @Turbots!

Describe the bug
Some recipes of the Spring Boot 2.4 to 2.5 Upgrade functionality are always shown as applicable.

To Reproduce

1. Run the demo-upgrade-spring-boot-report demo and upgrade the demo app to 2.5.x
2. Then scan the application again
3. The applied recipes for 2.4.x Spring Boot is still shown as applicable

Expected behavior
The 2.4 upgrade-related recipes should not be shown for any Spring Boot application with a version different from 2.4.x.

Additional context
For multiple of these recipes the condition is set to org.springframework.sbm.common.migration.conditions.TrueCondition which makes SBM always show it as applicable.

[fabapp2]

If boot-2.4-2.5-sql-init-properties gets applied after boot-2.4-2.5-datasource-initializer the properties used in the spring.datasource.schema-... properties added with DataSourceInitializerConfiguration get changed. This is wrong. Either provide order appropriately and add condition check to avoid showing boot-2.4-2.5-sql-init-properties as applicable after boot-2.4-2.5-datasource-initializer hjas been applied, or change property names in DataSourceInitializerConfiguration