0025: Introduce SDK Payload Tester

[tonyo]

In this RFC the Quality Engineering team introduces SDK Payload Tester (will be referred to as "Payload Tester" in the rest of the document) -- a new testing service to ensure better validation and integration testing of payloads produced by Sentry SDKs.

Rendered RFC

[HazAT]

So far, it makes sense to me, a few points to consider.

Requirement:

• Ideally, this runs before every release of an SDK and acts as some kind of "Percy" for HTTP payloads. Meaning before a release goes out, a dev needs to approve changes seen in the payload and confirm that the changes seen are expected.

Additional Features:

• A "Forward to Sentry button" is there where you can enter your DSN and this payload is forwarded to it so you can take a look in Sentry
• I want to be able to compare different versions of the same SDK to see what changed from one Major version to the other.
• A "SDK completion" Endpoint -> A new SDK can send a payload there and you get a checkmark that all important features are supported (or a Matrix). Think of it as a verifier for anyone who implements a Sentry-compatible SDK.