Grails 7.0.0 - Use Boot BOM property h2.version to control H2 version in Grails BOM

[boardbloke]

Feature description

H2 version in https://repo1.maven.org/maven2/org/apache/grails/grails-bom/7.0.0/grails-bom-7.0.0.pom is not pulled from Boot BOM and could be

https://repo1.maven.org/maven2/org/springframework/boot/spring-boot-dependencies/3.5.6/spring-boot-dependencies-3.5.6.pom

[boardbloke]

Actually might be a good idea to make every version defined in the Grails bom reference a property, and either use the one defined in the Spring BOM if it exists for that artefact, or create one (prefixed grails. so e.g. grails.xxx.version to avoid potential clashes with new properties created by spring in the future)

[jdaugherty]

Originally, we tried to eliminate any dependency in grails-bom that was also defined in the spring bom. It seems we missed h2, and the real solution here is to just remove h2 from the grails-bom. We're trying to stay in sync with Spring going forward, and not do overrides unless we have to.

[jamesfredley]

h2 was a special case early on in the Grails 7 journey where a few different sets of tests would not run on the latest version of h2. That was resolved over the 18 month period as the tests were updated. We can remove this in either 7.1.x or 8.0.x.

[matrei]

The same 2.3.232 version is in both grails-bom:7.0.1 and spring-boot-dependencies:3.5.7, so technically we should be able to remove it from grails-bom without issues.