Add artifact deployment to workflow_dispatch to keep client and agents in sync

[emerkle826]

Fixes #339

This will publish all of the project Maven artifacts at the same time as the Client jar so that downstream projects can access the same version of the agent(s) and server files as the client jarfile.

[Miles-Garnsey]

Suggestion: comment out artifactory related jobs and make a comment that they don't work at the moment.

[Miles-Garnsey]

@emerkle826 looks like we have failing tests here, happy to review once they're passing!

[emerkle826]

@Miles-Garnsey A re-run of the tests and they are all passing now. At some point I will dig into the flaky one as it's not always the same test, but usually the same symptom....

[Miles-Garnsey]

We've validated that manually running the Publish OpenAPI client does push both client and agent jars to Cloudsmith.

The workflow that is run is the one on the branch, not the one on main, so we have been able to validate this prior to merge.

Erik has confirmed that no rebase is applied to the branch prior to the new publication CI jobs running, so the commit sha from HEAD is the correct one to apply to the artifacts.

The only thing remaining prior to approval is to comment out the DataStax publication target, since that isn't working at present.

[Miles-Garnsey]

DataStax publication option is removed. This is ready for merge pending green CI.

[Miles-Garnsey]

CI is green, approving and merging.