The `error` and `load` events should be added to many interfaces

While demixing the onerror and onload event handlers from the GlobalEventHandlers mixins, @foolip had mentioned there are many other interfaces the event should be placed on as well.

This (the string "error") is probably the most widely used event type, fired in lots of places. For this cleanup we only need to worry about the Node hierarchy and Window, however.

There's already an entry for Window, and these are the elements I can find where there's an "error" event:

• HTMLImageElement
• HTMLLinkElement
• HTMLMediaElement (already in BCD)
• HTMLObjectElement
• HTMLScriptElement
• HTMLSourceElement
• HTMLStyleElement
• HTMLTrackElement
• SVGImageElement
• SVGScriptElement
• SVGStyleElement
• SVGUseElement

Originally posted by @foolip in https://github.com/mdn/browser-compat-data/pull/16610#pullrequestreview-1028234821

I've opened this issue to remind us to research this later, so that the removal of GEH isn't blocked on this.

Start by reviewing the existing Window and HTMLMediaElement entries, then research the Node hierarchy and the interfaces listed in the issue. Done means the applicable error and load events are represented on the relevant interfaces without blocking removal of GlobalEventHandlers.