Missing Cloudflare bindings often surface as runtime errors (e.g. 'DB binding not found') today.

Could we validate the required bindings (DB, BLOB, KV, CACHE or HYPERDRIVE, depending on the enabled Hub features) earlier in the process and display a clear error message during setup or build when targeting Cloudflare, especially when using Nitro's Wrangler/Deploy config generation?

This would improve the user experience by identifying misconfigurations before deployment/runtime.

Related: #716 (comment)