[DI-6749] Restore the autogenerated Currents events docs

[isturdy]

Why are you making this change? (required)

This adds payload documentation for non-Storage Currents destinations, as well as fixing numerous cases where the existing docs had fallen out of sync with what we actually send.

Related PRs, issues, or features (optional)

• BD-3611
• DI-6749

Feature release date (optional)

• N/A

Contributor checklist

• I confirm that my PR meets the following:
  • I signed the Contribution License Agreement (CLA).
  • My style and voice follows the Braze Style Guide.
  • My content contains correct spelling and grammar.
  • All links are working correctly.
  • If I renamed or moved a file or directory, I set up URL redirects for each file.
  • If I updated or replaced an image, I did not remove the original image file from the repository. (For more information, see Updating an image).
  • If my PR is related to a paid SKU, third party, SMS, AI, or privacy, I have received written approval from Braze Legal.

Submitting for review

If your PR meets the above requirements, select Ready for review, then add a reviewer:

• Non-Braze contributors: Add braze-inc/docs-team as the reviewer.
• Braze employees: Have any relevant subject matter experts (like engineers or product managers) review your work first, then add the tech writer assigned to your specific vertical. If you're not sure which tech writer to add, you can add braze-inc/docs-team instead.

Thanks for contributing! We look forward to reading your work.

[josh-mccrowell-braze]

Was this update intentional?

[isturdy]

Oops, no--just added it to get rake to work locally. Removed.

[vercel]

@isturdy is attempting to deploy a commit to the Braze team on Vercel, but is not a member of this team. To resolve this issue, you can:

• Make your repository public. Collaboration is free for open source and public repositories.
• Add @isturdy as a member. A Pro subscription is required to access Vercel's collaborative features.
  • If you're the owner of the team, click here and add @isturdy as a member.
  • If you're the user who initiated this build request, click here to request access.
  • If you're already a member of the Braze team, make sure that your Vercel account is connected to your GitHub account.

To read more about collaboration on Vercel, click here.

[vercel]

@rachel-feinberg is attempting to deploy a commit to the Braze team on Vercel, but is not a member of this team. To resolve this issue, you can:

• Make your repository public. Collaboration is free for open source and public repositories.
• Add @rachel-feinberg as a member. A Pro subscription is required to access Vercel's collaborative features.
  • If you're the owner of the team, click here and add @rachel-feinberg as a member.
  • If you're the user who initiated this build request, click here to request access.
  • If you're already a member of the Braze team, make sure that your Vercel account is connected to your GitHub account.

To read more about collaboration on Vercel, click here.

[rachel-feinberg]

Went through for a Docs review! LGTM

[flybonzai]

@josh-mccrowell-braze @rachel-feinberg who do we need to merge this?

[rachel-feinberg]

@flybonzai I merged it in! 😄