Avoid using DOMRect constructor for Edge and IE

[ellatrix]

Description

Fixes #19979. Not sure if this is the solution we want, but it does get rid of calling DOMRect.

How has this been tested?

Screenshots

Types of changes

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR.

[ellatrix]

@aduth I'm guessing you prefer the polyfill? :)

[aduth]

@ellatrix I’ve no preference for it if it can be easily avoided to remove DOMRect. I’m mobile currently but can check later if it’s simple enough to use plain objects. I’d wonder what purpose DOMRect would otherwise serve, or were just not using those features?

[aduth]

I'm struggling to see what might have been the original purpose to use DOMRect, other than as a known interface of properties (which can be helpful for type-checking, certainly).

https://developer.mozilla.org/en-US/docs/Web/API/DOMRect

I guess the only worry there would be is if we're passing around these rect objects to anything which explicitly requires instanceof DOMRect.

[aduth]

Polyfill alternative approach is at #20110