feat: forward @prismicio/react components through @prismicio/next

[angeloashmore]

Resolves: N/A

Description

This change simplifies the developer experience by forwarding common Prismic React components through @prismicio/next:

• Renames PrismicNextImage to PrismicImage (old name kept as deprecated alias)
• Renames PrismicNextLink to PrismicLink (old name kept as deprecated alias)
• Re-exports PrismicText, SliceZone, and related types from @prismicio/react
• Creates Next.js-specific PrismicRichText with optimized image/link defaults using next/image and next/link
• Creates Next.js-specific PrismicTable with optimized rich text defaults

Developers can now import most Prismic React components directly from @prismicio/next without needing to import from @prismicio/react separately.

Note: This PR depends on prismicio/prismic-react#241 for the RichTextComponents type alias.

Checklist

• A comprehensive Linear ticket, providing sufficient context and details to facilitate the review of the PR, is linked to the PR.
• If my changes require tests, I added them.
• If my changes affect backward compatibility, it has been discussed.
• If my changes require an update to the CONTRIBUTING.md guide, I updated it.

Preview

N/A

How to QA ¹

1. Install the updated package
2. Verify imports work:

   import { PrismicImage, PrismicLink, PrismicText, SliceZone, PrismicRichText, PrismicTable } from "@prismicio/next";
   import { PrismicNextImage, PrismicNextLink } from "@prismicio/next"; // deprecated but works

3. Verify PrismicRichText renders images using next/image and links using next/link
4. Verify deprecated aliases show TypeScript deprecation warnings

🤖

Footnotes

1. Please use these labels when submitting a review:
   ❓ #ask: Ask a question.
   💡 #idea: Suggest an idea.
   ⚠️ #issue: Strongly suggest a change.
   🎉 #nice: Share a compliment. ↩