feat: backport extended media API response

[lihbr]

Types of changes

• Chore (a non-breaking change which is related to package maintenance)
• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Related: https://github.com/prismicio/prismic-web/pull/134

@prismicio/react still relies on @prismicio/richtext which relies on @prismicio/types. This makes types expected from @prismicio/react inconsistent with types generated from @prismicio/client. This PR backports new media API response types for types to match (which perhaps also solves other problems)

In the near future I think we'll need a plan to update @prismicio/react not to use @prismicio/richtext anymore but @prismicio/client/richtext instead (which was my plan first, but I wasn't sure how you wanted to handle the peer dependency of @prismicio/client then as I don't think it can be promoted to a regular dependency there? (that's how it's done with Vue.js though 🤷‍♀️)

Checklist:

• My change requires an update to the official documentation.
• All TSDoc comments are up-to-date and new ones have been added where necessary.
• All new and existing tests are passing.

[angeloashmore]

Let's go with this fix for now. The long-term fix is what you described: update @prismicio/react (and others, maybe) to use @prismicio/client/richtext. That will probably be best done in a major version—something we won't do until at least next quarter.