Submit new Service Ping with fallback solution

We want to submit the new Service Ping instead of the legacy Usage Ping. However, to make sure that this works without any issues when rolling it out, we want to use the previous Usage Ping payload as a fallback.

Related MRs:

• !64500 (merged)
• !65336 (merged)

Requirements

• Use new BuildPayloadService to submit new service ping data
• If building the new payload, or submitting the new payload to the Version app fails (anything except HTTP 200 OK) , we want to rescue and use the "legacy" Usage Ping data instead

Open Question

• Do we have logs for the version-app to track errors?