Update ModuleDescriptor identifiers in the Gradle workflow

[alb3rtino]

Purpose

The Gradle workflow publishes the ModuleDescriptor as built. Every snapshot build therefore has the same id (e.g. mod-agreements-7.4.0-SNAPSHOT, without the build number of the Docker tag). The registry accepts the first publish and rejects every later one with status 400.

In mod-agreements the first master run after the migration (#15) published, and the two runs since failed in "Publish ModuleDescriptor": #29 and #32. The other four Gradle modules have had one master run each and will fail on their next one.

Approach

Add a step to gradle-build.yml that sets the id from the artifact version, with the same jq expression as maven-module-descriptor-get.yml. This aligns the Gradle workflow with the Maven workflow, whose style #165 set out to follow.

On top of that, the expression sets launchDescriptor.dockerImage and launchDescriptor.dockerPull, as it does for Maven. Until now the Gradle descriptor names the image without the Docker Hub organization and has dockerPull false.

The step is tested locally against the mod-agreements descriptor and a local Okapi.

Additional observation

The Maven workflow runs an Okapi dependency check for release builds. The Gradle workflow has none.

[dcrossleyau]

@david-igbinedion and @alb3rtino -- I do not see any testing at mod-agreements. Today i created a release at .github as v1.17.5 so that means that this is now included in the default @v1 being used by the Workflow at mod-agreements.

Please monitor the relevant Action runs at a Gradle-based repository to ensure that this Workflow now has the desired outcome.