Conformance profile should not upload if already exists

[sjberman]

When we create a release, all the conformance jobs will attempt to upload the conformance report. Only the first one wins, and all the rest will fail since the report already exists.

Acceptance

• When a release occurs, the first conformance job to finish will upload the report, and all subsequent jobs should skip this step and not fail.

[lucacome]

Why are we uploading the report to the release? Do we still need to do that? Can we just upload it as an artifact to the run?

[sjberman]

@lucacome It's a way to show our conformance publicly for each of our releases, as well as make it very easy for whoever does the release to grab the report to upload to the Gateway API repo. As of right now, we haven't had any use for saving the conformance report per run.

[lucacome]

I thought maybe if it was just for us to grab to upload it to the Gateway API repo, it could be enough to just upload it as an artifact instead of the release, I wasn't sure if people were interested in downloading it as well.