Upload results.json using raw api, rather than test-collector

[IanButterworth]

Redo of #428
Incorporates #430

It's too difficult to use test-collector to upload these files with a custom job-id, and #428 did it in an unsafe way.

[IanButterworth]

Fixes this from JuliaLang/julia#57686

2025-03-09 20:18:09 INFO   Found 1 files that match "results_ArgTools_1.json"
fatal: failed to upload artifacts: uploading artifacts: creating uploader: invalid upload destination: 'results_Artifacts_1.json'. Only s3://*, gs://*, rt://*, or https://*.blob.core.windows.net destinations are allowed. Did you forget to surround your artifact upload pattern in double quotes?

[IanButterworth]

@staticfloat is this ok? One regression is the plugin did parallel uploads, which isn't an issue on julia master because we only have one results file, but with JuliaLang/julia#57686 we will have many.

I was thinking of merging this and testing it on that PR to see if I need to add the parallel uploads back?

[vchuravy]

I don't think we need parallel uploads here.

[vchuravy]

The only thing would be to open an issue with the test collector plugin and ask for support of a custom job_id

[IanButterworth]

The only thing would be to open an issue with the test collector plugin and ask for support of a custom job_id

Already open buildkite-plugins/test-collector-buildkite-plugin#83
And a PR buildkite-plugins/test-collector-buildkite-plugin#84 but the PR doesn't work because the env in the pre-exit process doesn't see new env vars from the previous steps (and sourcing the env var file proved a bad idea because of buildkite/agent#3227)

[staticfloat]

Belated LGTM!