Gradle cannot build effective model because of failure in pom.xml

## Situation
Our build had some errors outputs from Gradle at at https://github.com/mercedes-benz/sechub/issues/1658.
The reason was the usage of spotless which relies on JDT parts for automated eclipse formatting.

Following output was shown multiple times:
```
Errors occurred while build effective model from /home/runner/.gradle/caches/modules-2/files-2.1/org.eclipse.platform/org.eclipse.core.expressions/3.8.200/eb159f34083b0135459745f934a6ad5eb61b61c/org.eclipse.core.expressions-3.8.200.pom:
'modelVersion' must be one of [4.0.0] but is '4.0'. in org.eclipse.platform:org.eclipse.core.expressions:3.8.200

```
Looking at
https://repo1.maven.org/maven2/org/eclipse/platform/org.eclipse.core.expressions/3.8.200/org.eclipse.core.expressions-3.8.200.pom

The `pom.xml` contains
```4.0```

The older version (3.8.100) https://repo1.maven.org/maven2/org/eclipse/platform/org.eclipse.core.expressions/3.8.100/org.eclipse.core.expressions-3.8.100.pom contains correctly:
```4.0.0```

## Wanted
A gradle build shall have not those warnings when there is a gradle/maven dependency to `org.eclipse.core.expressions`

### Suggested solution
- Change the pom model settings (sorry I did not find the part inside the sources) so next releases have `4.0.0` inside
- Maybe change the existing deployed `pom.xml` at maven central to correct version in `pom.xml` for `org.eclipse.core.expressions-3.8.200` - if possible

Inizia confrontando l’org.eclipse.core.expressions-3.8.200.pom distribuito con la versione 3.8.100 su Maven Central, quindi traccia il codice sorgente o la configurazione di release di Eclipse Platform che produce questo pom.xml. Esegui la build Gradle che utilizza la dipendenza e verifica che l’avviso relativo al modello effettivo non venga più visualizzato.

Scritto dal modello di indicizzazione a partire dal testo della issue.