Research how to harden common endowments

[Montoya]

This ticket should focus on finding a way how to harden specific endowments such as endowments that are constructor functions.

One of the suggestion was using Proxies, so that should be one of the starting points for this research.

This ticket will unblock and refine the following tickets:
#1018
#1017

In general, constructor functions are target for the hardening and are presented in the table below:

Endowment	Type
BigInt	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

[david0xd]

After consulting with a Security Team, we identified some approaches how this should be done.
There are two phases of testing identified:

1. Trying to make changes to the endowments which should not be possible at all (hardening with harden() SES function).
2. Searching all objects for globalThis references which exposure to the snap should be prevented.

Several testing approaches are implemented to ensure the security.
Further manual in-detail security audit of the JavaScript intrinsic objects might be required to fully confirm security of it which possibly can be addressed in the two remaining tickets in this epic.

[david0xd]

Since this is already done and discussed, I will close this ticket.