A publish answer that didn't come from the artifact service is reported as a relay error with its status.
What's wrong with this entry?
When a publish, deploy or upload answer did not actually come from the artifact service, it is now reported as a relay error carrying the HTTP status and a message saying the publish was not completed, instead of being parsed as if it were a deploy result.
- Responses carry a marker recording whether they came from the artifact service itself.
- New telemetry reasons:
relay_error,upload_relay_error,prepare_upload_relay_error. - The related HTTP call sites dropped their per-call host, auth and status-validation options.
prepare_upload_relay_error
Strings lifted out of the shipped bundle, so the claim above can be checked against them.