feat: migrate the contract account data structure to kakarot-ssj

[Eikix]

Feature Request

In Kakarot Cairo 0, to mimic the EVM contract accounts (Smart Contracts), we use Starknet contracts.
Source:

• https://github.com/kkrt-labs/kakarot/blob/main/src/kakarot/accounts/contract/library.cairo
• https://github.com/kkrt-labs/kakarot/blob/main/src/kakarot/accounts/contract/contract_account.cairo

Each contract_account needs:

Tasks

Beta Give feedback

1. to store its EVM bytecode (post-constructor EVM Bytecode)
2. have the main kakarot contract as its owner (blocked by kakarot main smart contract being created, but can just create the constructor and logic before hand)
3. be upgradable, by using the new syscall replace_class -> upgrade should be only accessible by either kakarot main SC or a specific role, UpgradeAdministrator (can be a multisig at first)
4. to respect the current API https://github.com/kkrt-labs/kakarot/blob/main/src/kakarot/accounts/contract/contract_account.cairo
5. the implementation should be thoroughly tested

Note that for storing its own bytecode we can:
Use storage index: Besides storing 32/16 bytes for each storage, once the hash for the storage location is calculated we can access up to 256 more slots by adding to the index.

Milan made a cool Alexandria storage list lib for this, we can use it here.

Additional Context

If the feature request is approved, would you be willing to submit a PR?
(Help can be provided if you need assistance submitting a PR)

• Yes
• No

[Eikix]

Linked to #55 and #134
All three will be closed at the same time

[Eikix]

Important update: we are gathering some bugs in the Kakarot v0 codebase, we need to make sure each issue and each PR in Kakarot-ssj is aware of the lists of known bugs. Look at this link everytime you take an issue and check your issue isn't targeted by a known bug.

[Eikix]

Important update: we are gathering some bugs in the Kakarot v0 codebase, we need to make sure each issue and each PR in Kakarot-ssj is aware of the lists of known bugs. Look at this tracking issue everytime you take an issue and check your issue isn't targeted by a known bug. Will add this reminder in many places to make sure we keep track of known bugs.

[Eikix]

Closing this issue for now as Contract Account will not be an individual Starknet smart contract but rather a storage struct inside KakarotCore