Remove globals from Web/API

[wbamberg]

This issue is to remove "globals" from Web/API, by instead having separate pages under Window and WorkerGlobalScope. This was discussed in https://github.com/orgs/mdn/discussions/360.

This has been done for indexedDB (#32040) and looks all right (https://github.com/orgs/mdn/discussions/360#discussioncomment-9023867), so let's do it for all the remaining pages.

• indexedDB
• crypto
• fetch
• performance
• origin
• isSecureContext
• crossOriginIsolated
• reportError
• btoa
• atob
• setTimeout
• clearTimeout
• setInterval
• clearInterval
• queueMicrotask
• createImageBitmap
• structuredClone
• scheduler
• caches
• trustedTypes

For each page, the process is:

• yarn content move the global page to be under Window.
• update the page under Window to be an instance property or method page, and update the content accordingly
• create a new version of the page as an instance property or method page under WorkerGlobalScope, that's worker-specific
• manually delete the redirect from Web/API/WorkerGlobalScope/indexedDB to Web/API/indexedDB
• fix any domxref links so they don't incur redirects
• update GroupData, adding entries for the two new pages into the entry for the API that defines the feature (e.g. Indexed DB API).

---

Once all pages are fixed, the final step in this issue is to remove the web-api-global-function and web-api-global-property page types.

• Remove global page types

[skyclouds2001]

Also, should the same thing to be done on BCD?

[wbamberg]

Also, should the same thing to be done on BCD?

@Elchi3 , @queengooborg, wdyt?

[Josh-Cena]

I had been asking about this in Slack but Vinyl did not seem particularly interested—or perhaps I didn't explain it well.

[skyclouds2001]

seems mdn/browser-compat-data#18739 is already discussing this issue