Additionally harden common endowments

[david0xd]

Previously common (now custom) endowments should be hardened in a more proper way after the first iteration that is followed in this ticket: #1015 (PR: #1058)

This ticket is part of an epic: #585

Constructor functions are target for the hardening in this ticket and are presented in the table below:

Endowment	Type
BigInt	constructor
Date	constructor
SubtleCrypto	constructor
TextDecoder	constructor
TextEncoder	constructor
URL	constructor
Int8Array	constructor
Uint8Array	constructor
Uint8ClampedArray	constructor
Int16Array	constructor
Uint16Array	constructor
Int32Array	constructor
Uint32Array	constructor
Float32Array	constructor
Float64Array	constructor
BigInt64Array	constructor
BigUint64Array	constructor
DataView	constructor
ArrayBuffer	constructor
AbortController	constructor
AbortSignal	constructor

Additional hardening methods that should be considered in this work are a proxy or a specific wrapper that will be the outer shell of an instance of a specific class.

[Montoya]

Consider using proxies instead of hardening each individual endowment with custom wrappers, and only harden the return if it returns something other than itself.