perf: change payload type of replay event

[anonrig]

Previously, we were using a unoptimized data structure. This change makes sure that we don't break production and also make the transition to a better one.

Ref: getsentry/snuba#5831
Ref: getsentry/sentry#69916

[github-actions]

versions in use:

The following repositories use one of the schemas you are editing. It is recommended to roll out schema changes in small PRs, meaning that if those used versions lag behind the latest, it is probably best to update those services before rolling out your change.

• getsentry/snuba: pip:sentry-kafka-schemas==0.1.72 (upgrade)
• getsentry/snuba: rust:sentry-kafka-schemas==0.1.72 (upgrade)
• getsentry/sentry: pip:sentry-kafka-schemas==0.1.74

latest version: 0.1.74

benign changes

schemas/ingest-replay-events.v1.schema.json

• {"path": ".payload", "change": {"TypeAdd": {"added": "string"}}}
  

• {"path": ".payload", "change": {"TypeAdd": {"added": "number"}}}
  

• {"path": ".payload", "change": {"TypeAdd": {"added": "integer"}}}
  

• {"path": ".payload", "change": {"TypeAdd": {"added": "object"}}}
  

• {"path": ".payload", "change": {"TypeAdd": {"added": "boolean"}}}
  

• {"path": ".payload", "change": {"TypeAdd": {"added": "null"}}}
  

✅ This PR should be safe to roll out to consumers first. Make sure to bump
the library in the following repos first:

getsentry/snuba
getsentry/super-big-consumers

...then in the other repos:

getsentry/sentry

Take a look at the README for how to release a new version of sentry-kafka-schemas.