Packaging configuration refactoring

See merge request !6

Keeping artifact forever is not possible on a per project basis according to https://gitlab.com/gitlab-org/gitlab/-/issues/22761#note_390161695

- CI no longer publish artifacts in GitLab package repository. Instead we deploy the binaries using files stored by GitLab pipelines.
- Pipeline artifact retention duration is different depending on the branch that trigger the build.
- Job that build the data collection jar file now also store dependencies lib folder as persistent artifacts.
- Maven CLI options are now stored in `.mvn/maven.config` in order to be shared both by Maven run locally and by CI jobs.
- Remove all references to configuration file from CI configuration and Maven build files.
- WebApp configuration file location is now defined by a JVM system property: `mrl.conf.file.path`.
- Add Maven wrapper to use same Maven version when building locally.

Rely on GitLab CI variables, Maven properties and Maven war plugin filtering.

When Sonar computes no test_success (some languages like Perl), assume 100% success if tests are present. Closes #70

Implement requied changes (see #48)

Renamed aggregates com_* to cty_*, added OMM_DOC metric to cty_omm, updated thresholds for RatioNoLic

Name need to be coherent with name in XWiki:
- `rocket-chat` (not `rocket`)
- `imixs-workflow` (not `imixs`)

The SQL query in `fetchMKTMetrics` method was using hard-coded project name (`asm`) instead of using the `DatasetFactory` `project` attribute.

Also update JUnit and MariaDB version.