What?

Consuming an API with active fetch cache can return 200 responses at one point which land in the fetch cache. If now subsequent requests of the same route return 404 (e.g. in a webshop an article got deactivated), the fetch cache still returns stale data. More details: #62920

Why?

Patched fetch does the subsequent http call anyways, just the stale data is returned.

How?

Allowing patch-fetch to override existing cache entries with status 404. There might be alternative solutions to this, but I didn't see a method to just remove the cache entry here and returning the new data.

Adding testcase to make multiple http calls in jest where the first call is returning 200 status and the second 404.

Fixes #62920