By default, new Jira CLI versions send anonymous
analytics information to their systems.

While that's not a problem for us, the real problem
is that to perform those actions, each time Jira CLI
is invoked, a new process is spwaned to send that
analytics and/or logging information. And the process
never ends!

So, after 100 jobs using Jira CLI, we have 100 of those
processes running. Crazy!

Surely it's a bug a maybe it's already fixed in more recent
Jira CLI versions (10.5.0 is the latest, we are running right
now 10.0.0).

But, as a quick fix, with this we'll stop those processes
completely, by explicitly opting out from analytics (default
to true) and logging (default to false, but let's specify it too).

Note that to get this configuration being used, we need to add
to the "jiraclicmd" global this:

-DACLI_SERVICE_CONFIG=/path/to/this/acli-service.properties

(the file itself has details about how to configure it)

While our final CLI target is 10.5.0 (and it was added by
!1), right now the tracker has the 9.9.0
connector and it's too old for the 10.5.0 CLI version.

So, to be able to test everything, we are going to use the CLI
10.0.0 in the interim (that is compatible with the Tracker connector).

And, in few days/weeks, when the Tracker is updated (and the connector
on it is also updated to 10.x), we will change the jenkins controllers
to use the final CLI 10.5.0 version.

And this 10.0.0 interim CLI will be deleted.

Add atlassian cli 10.5.0

See merge request !1

We are moving all our integrations from old 6.6.0 to actual 10.x
one @ https://tracker.moodle.org/browse/MDLSITE-7033

So better we have it at hand in CI servers to go testing and making
the switch. Still no script uses it, so cannot break anything.

Note it has changed of name ("atlassian-cli" folder vs "acli" monolithic jar)
but that's how it comes now from upstream downloads.