chore: add e2e for forbidden and unauthorized

[sommeeeer]

• Add e2e test for forbidden and unauthorized (Next.js blog)
• Next will set cache-control to s-maxage=31536000 on those routes, so i added 403 and 401 in fixHeadersForError() so they don't get cached

[changeset-bot]

⚠️ No Changeset found

Latest commit: ae48e5c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in Stackblitz

pnpm add https://pkg.pr.new/@opennextjs/aws@669

commit: ae48e5c

[conico974]

We should probably wait a bit before merging this one, not sure what's the point of using forbidden or unauthorized on SSG route ( And they don't seem to work in middleware either )