Support passing a AbortSignal to cache.match

[SamyPesse]

Because of how Cloudflare is tracing async executions (https://zuplo.com/blog/2022/03/04/the-script-will-never-generate-a-response), when implementing concurrent logic with Promise.race or similar, it's prefered to use a signal to abort any underlying fetch.

For example in my case I want to read from multiple caches in parallel, and one of them is the caches.default. But in theory the script might respond before all the caches finished responding.

It'd be great if we could pass a AbortSignal to cache.match:

const abort = new AbortController();
const response = await cache.match(request, { signal: abort.signal });

[jasnell]

fyi ... @irvinebroque

[jasnell]

While we do already have some variances from the standard Cache API (https://developer.mozilla.org/en-US/docs/Web/API/Cache/match) I would be hesitant adding a non-standard option for a signal here. My preference would be to try to have the standard options updated to include a signal option that would parallel the option in fetch.

On a technical level, implementing this would not be difficult, however, and I think it would be a valuable addition.