Review approach to AIP010KeyValueStorage

[fulldecent]

This project makes the assertion:

Best practice with Aion is to explicitly define all storage locations using an enum and then use these enums for all calls to putStorage. This avoids overlapping storage, which is also a vulnerability.

And the potentially controversial:

Also, use static storage only for recursive call state and configuration options which apply to all onchain transactions.

Seeking to review this statement with AVM team to ensure we are aligned.

Additionally we find that the current API for storing to blockchain is likely to (and may actually have) result in insecure applications.

Upstream ticket: aionnetwork/AVM#399

[fulldecent]

Reported upstream to aionnetwork/AVM#402. Not a blocker for this implementation.