When an edge function uses read, it needs to fetch the file. This can result in a 401 Unauthorized error if Vercel's deployment protection is enabled.

This PR adds the automatically generated secret to bypass the protection when fetching the file. However, the user must have enabled protection bypass automation for it to work. See https://vercel.com/docs/deployment-protection/methods-to-bypass-deployment-protection/protection-bypass-automation

Not sure how to detect if the deployment is protected or not so we can tell the user to enable bypass if they run into a 401 error. Is it enough to throw this error if we receive the 401 error regardless of if protection has been enabled?

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

No test unless we can get a test app deployed through CI and perform playwright tests on it from there.

Tests

• Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

• Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.