Do not use per profile modules

ATM, Accounts use a couple of profiles to enable/disable sets of modules so that it is possible to build just a part of the source tree faster. The default profile does not include samples and integration tests. To enable all available modules, one has to activate sample and itest profiles. This setup causes problems in several common situations, e.g. when invoking mvn clean, mvn versions:set or releasing one has to activate the named profiles too, so that Maven does what one expects.

Hence, the current objective is to remove the per profile module sets and have just one default modules set including all available modules.

To reach the original goal of building fast through omitting long lasting parts, other strategies should be used, e.g. -DskipTests or other custom properties or even profiles that would disable some plugin executions rather than excluding whole modules.