Harden custom and common endowments and add tests

[david0xd]

This ticket is part of an epic: #585

The purpose of this task is to introduce and test SES security functionalities in order to secure a custom and common endowments that are part of the snaps-execution-environments package.

Acceptance criteria:
Harden all custom endowments in the endowments folder and add tests.
Test common endowments security.

Notes:
This task will continue more organized and reasonable work after the spike research: #1003

[kenhkan]

Hey team! Please add your planning poker estimate with Zenhub @david0xd @FrederikBolding @GuillaumeRx @hmalik88 @Mrtenz @ritave

[david0xd]

Since this ticket was the research around the endowment security and some experimental development. I will close this ticket, and consider it done.

The work after the research is split, and followed in this ticket at first: #1018
The PR with code changes is related to the ticket mentioned above and is here: #1058

Results of the research done within this ticket:

• Established and implemented way of testing and hardening common JavaScript (default) endowments.
• Established the security related work process and organization between the Snaps and Security team.
• Identified potential security threats with some of the endowments which are tracked in a separate tickets (Harden WebAssembly by allowing it to be used only through permission #1150 Implement custom security for Events #1132).
• Identified a specific need for hardening and paying more attention to the process for snap and ethereum endowment (Additionally harden custom endowments #1017).