Move cargo.run configuration for h2 database from the enterprise to the community release pom

To avoid differences between runtime environments consolidate the cargo.run profiles .

The h2 database was added to the Tomcat classpath in the enterprise release pom for BT-1677/ENT-943. This results in different configurations (and potentially different h2 releases on the classpath). As both h2.version and h2.database.version properties are used for the h2 database driver bundled with the repository and the h2 driver put on the Tomcat classpath setting the driver version to use is challenging. 

The release pom contains profiles for database driver selection such as MySQL/Postgres so ideally the h2 driver is handled in a similar way but that will take more work refactoring the repository and tooling using h2.

To make sure the h2 driver used is the same version for both embedded and provided instances the version needs to be set in the project pom instead of the release pom.