Add CI upload junit xml test results

[jerabekjiri]

This PR adds storing Hub unit test results in jUnit XML file when the test are running and then uploading them to the platform readiness dashboard.

Issue: https://issues.redhat.com/browse/AAP-29782

Documentation: handbook.eng.ansible.com/docs/Testing/xunit-junit

copy-pasted from https://github.com/ansible/aap-gateway/pull/527

[jctanner]

Why disable linting?

[jerabekjiri]

Why disable linting?

@jctanner that was just for testing

[jerabekjiri]

EDIT: failure is related to missing vars and secrets in my fork, this should work correctly in ansible repo

---

upload fails with

Run curl -v --user ":" --form "xunit_xml=@/tmp/galaxy_ng-test-results.xml" --form "component_name=hub" --form "git_commit_sha=c19e6ea4d34773d9a5e21f3cb95b6656f4b0891f" --form "git_repository_url=https://github.com/ansible/galaxy_ng" "/api/results/upload/"
curl: (26) Failed to open/read local data from file/application

(https://github.com/ansible/galaxy_ng/actions/runs/10788270380/job/29918687050?pr=2257#step:9:13)

looks like we're missing org variables: `PDE_ORG_RESULTS_AGGREGATOR_UPLOAD_USER, PDE_ORG_RESULTS_UPLOAD_PASSWORD, PDE_ORG_RESULTS_AGGREGATOR_UPLOAD_URL``

[jctanner]

Given the run_units.sh script executes inside the "pulp" container, how does the action-runner machine access /tmp/galaxy_ng-test-results.xml? Is there a volume mount to /tmp that I wasn't aware of?

[jerabekjiri]

Given the run_units.sh script executes inside the "pulp" container, how does the action-runner machine access /tmp/galaxy_ng-test-results.xml? Is there a volume mount to /tmp that I wasn't aware of?

@jctanner good catch, I forgot this is executed inside the container

Updated to curl in the pulp container, does this work for you?

[jctanner]

Seems fine as long as it does what it is supposed to.

[jerabekjiri]

Merged, the only way to test this is in production