This ensures we publish under separate tag for v14 backports.

<!-- Thanks for opening a PR! Your contribution is much appreciated.To make sure your PR is handled as smoothly as possible we request thatyou follow the checklist sections below.Choose the right checklist for the change(s) that you're making:## For Contributors### Improving Documentation- Run `pnpm prettier-fix` to fix formatting issues before opening thePR.- Read the Docs Contribution Guide to ensure your contribution followsthe docs guidelines:https://nextjs.org/docs/community/contribution-guide### Adding or Updating Examples- The "examples guidelines" are followed from our contributing dochttps://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md- Make sure the linting passes by running `pnpm build && pnpm lint`. Seehttps://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md### Fixing a bug- Related issues linked using `fixes #number`- Tests added. See:https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs- Errors have a helpful link attached, seehttps://github.com/vercel/next.js/blob/canary/contributing.md### Adding a feature- Implements an existing feature request or RFC. Make sure the featurerequest has been accepted for implementation before opening a PR. (Adiscussion must be opened, seehttps://github.com/vercel/next.js/discussions/new?category=ideas)- Related issues/discussions are linked using `fixes #number`- e2e tests added(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)- Documentation added- Telemetry added. In case of a feature if it's used or not.- Errors have a helpful link attached, seehttps://github.com/vercel/next.js/blob/canary/contributing.md## For Maintainers- Minimal description (aim for explaining to someone not on the team tounderstand the PR)- When linking to a Slack thread, you might want to share details of theconclusion- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues- Add review comments if necessary to explain to the reviewer the logicbehind a change### What?### Why?### How?Closes NEXT-Fixes #-->

…72153)### WhatBackport#65102,#65343 (as they are fixing the same issue)x-ref:[slack](https://vercel.slack.com/archives/C0676QZBWKS/p1730402565599979?thread_ts=1729588414.805619&cid=C0676QZBWKS)---------Co-authored-by: Zack Tanner <1939140+ztanner@users.noreply.github.com>

When `pages/500` uses `getStaticProps` we can honor staticallygenerating the page but we can't send a `Cache-Control` with`stale-while-revalidate` as we shouldn't be caching errored pages ever.This ensures we handle that case and add a regression test for it.<!-- Thanks for opening a PR! Your contribution is much appreciated.To make sure your PR is handled as smoothly as possible we request thatyou follow the checklist sections below.Choose the right checklist for the change(s) that you're making:## For Contributors### Improving Documentation- Run `pnpm prettier-fix` to fix formatting issues before opening thePR.- Read the Docs Contribution Guide to ensure your contribution followsthe docs guidelines:https://nextjs.org/docs/community/contribution-guide### Adding or Updating Examples- The "examples guidelines" are followed from our contributing dochttps://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md- Make sure the linting passes by running `pnpm build && pnpm lint`. Seehttps://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md### Fixing a bug- Related issues linked using `fixes #number`- Tests added. See:https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs- Errors have a helpful link attached, seehttps://github.com/vercel/next.js/blob/canary/contributing.md### Adding a feature- Implements an existing feature request or RFC. Make sure the featurerequest has been accepted for implementation before opening a PR. (Adiscussion must be opened, seehttps://github.com/vercel/next.js/discussions/new?category=ideas)- Related issues/discussions are linked using `fixes #number`- e2e tests added(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)- Documentation added- Telemetry added. In case of a feature if it's used or not.- Errors have a helpful link attached, seehttps://github.com/vercel/next.js/blob/canary/contributing.md## For Maintainers- Minimal description (aim for explaining to someone not on the team tounderstand the PR)- When linking to a Slack thread, you might want to share details of theconclusion- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues- Add review comments if necessary to explain to the reviewer the logicbehind a change### What?### Why?### How?Closes NEXT-Fixes #-->

backport#71723