Fix Maven options interpretation during CI build

[lemeurherve]

Description

This PR fixes tags publication by actually passing OPTS as env var to maven script.

Fixup of:

• Disable spotless on tag #484

Testing done

Successful replay of the 3.8.0 tag on infra;ci.jenkins.io

Submitter checklist

Beta Give feedback

1. If an issue exists, it is well described and linked in the description
2. The description of this pull request is detailed and explain why this pull request is needed
3. The changeset is on a specific branch. Using feature/ for new feature, or improvements ; Using fix/ for bug fixes ; Using docs/ for any documentation changes.
4. If required, the documentation has been updated
5. There is automated tests to cover the code change / addition or an explanation why there is no tests in the description.

[alecharp]

I'm surprise this is necessary as the previous release replay (3.7.1) was successful..

[lemeurherve]

I'm surprise this is necessary as the previous release replay (3.7.1) was successful..

The replay wasn't exactly the same (my mistake, sorry), it was still using """ instead of ''' thus $OPTS was interpolated by Groovy.

Using ''' is safer.