feat(v6): update cloudflare default image service

[Princesseuh]

Description (required)

withastro/astro#15435 changes the default to use the bindings instead of compile because compile's dev behavior is not intuitive anymore (yet)

[netlify]

✅ Deploy Preview for astro-docs-2 ready!

Name	Link
🔨 Latest commit	c7af404
🔍 Latest deploy log	https://app.netlify.com/projects/astro-docs-2/deploys/699c346257a1e200081562ef
😎 Deploy Preview	https://deploy-preview-13267--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 project 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/guides/integrations-guide/cloudflare.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.

[sarah11918]

Just noting that this will need an entry in the Cloudflare upgrade guide here too, where the change is clearly noted and with any upgrade guidance! https://v6.docs.astro.build/en/guides/integrations-guide/cloudflare/#upgrading-to-v13-and-astro-6

Normally when a default setting has changed, we say things like "inspect your deployed project for anything funky" in case this affects them. And if possible, we like to give advice on what to do to "revert to the previous behavior" (since presumably that was already working), which in this case seems to be explicitly setting imageService: "compile"

Edited to add: Will note that this won't go in the main v6 upgrade guide since it's just for Cloudflare, but you can see what other "Changed default" entries typically look like there for inspiration! https://v6.docs.astro.build/en/guides/upgrade-to/v6/#changed-defaults

[sarah11918]

This should still say what it uses, like all the other options, since this option is to define which image service is being used.

And, is the previous sentence now incorrect, that all astro:assets features are disabled for pages rendered on demand? That seemed a very clear way of stating it, so if it hasn't changed, I'm wondering why the wording has? Or do you want to emphasize the passthrough runtime behaviour? If so, then I'd write passthrough in code, something like:

Suggested change

	- **`compile`:** Transforms images at build time for pre-rendered routes. Uses passthrough for on-demand rendered pages.
	- **`compile`:** Uses XXXXXXX to transform images at build time for prerendered routes. The noop `passthrough` option is configured for on-demand rendered pages.

(Also, note that we're standardizing docs around prerendered (no hyphen) as we get around to them, so might as well update that here!)

[OliverSpeir]

c7af404

The reason it just says locally instead of explaining exactly what it uses to transform is because its using sharp but through miniflare so its not exactly the same as it was before when we just said it uses sharp