fix(adapter-node): only send cache header when static resource is 200

[cdemi]

Fixes #9393

During gradual deployment of an app with multiple instances, it is possible to load the main page from one server and the second request for static content goes to a server that has the old code deployed on it.

The old server, with the old code, does not yet have the new file, therefore it returns 404. So far, so good.

The problem arises, that with the return of 404, it also sends cache-control header with a high max-age and immutable. The browser and intermediate CDNs cache this response as much as they can.

Therefore even after the new server gets the new app, the CDNs and the browser need to force cache clear in order to be able to get the new static files.

It would make sense that unless the response is 200, the cache header is not sent

I have not managed to write a test for this use case, if someone could help I would be really grateful. I am also not sure if I managed to do the changeset correctly.

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. adapter-node sends cache headers when static files are 404 #9393
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

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:.