fix: update type of CollectionEntry ids

[fedetibaldo]

Description (required)

The legacy content collections were generating an union of all possible ids. This is no longer the case--it's just a string. This change reflects that.

First-time contributor to Astro Docs?

Yes. @fedetibaldo is my handle on Discord

[netlify]

✅ Deploy Preview for astro-docs-2 ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	6034a1d
🔍 Latest deploy log	https://app.netlify.com/sites/astro-docs-2/deploys/680261aad2a8bb000893d2c9
😎 Deploy Preview	https://deploy-preview-11435--astro-docs-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[astrobot-houston]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
en/reference/modules/astro-content.mdx	Source changed, localizations will be marked as outdated.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[astrobot-houston]

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉

Here’s what will happen next:

1. Our GitHub bots will run to check your changes.
   If they spot any broken links you will see some error messages on this PR.
   Don’t hesitate to ask any questions if you’re not sure what these mean!

2. In a few minutes, you’ll be able to see a preview of your changes on Netlify 🥳.

3. One or more of our maintainers will take a look and may ask you to make changes.
   We try to be responsive, but don’t worry if this takes a few days.

[sarah11918]

Thanks for your patience, @fedetibaldo , while we're a little behind with docs PRs while we've been getting things ready and out for Launch Week!

I'm going to ask @ArmandPhilippot to review this PR for you. I suspect that it is correct as stated: the "Example Type" is meant to give an example as to what the (yes, string) might look like. I believe the type given is shown as an example to be more helpful than just saying that the type will be string, but I will let Armand continue with this PR as he has been helping us standardize our reference types/examples!

[ArmandPhilippot]

This is indeed correct. I believe the Example Type is rather what we used with the legacy API and we forgot to update that. I think this change will be more useful because it doesn't imply that autocomplete can be expected here.

Thanks @fedetibaldo and sorry for the delay! Welcome to Team Docs. 🥳