Feat/add upgradabeality to eoa

[bajpai244]

Pull Request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build-related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

This PR adds upgradeability to the EOA contract.

Resolves: #433

What is the new behavior?

The EOA is now an upgradeable contract.

Does this introduce a breaking change?

• Yes
• No

[enitrat]

@Eikix can you review

[Eikix]

lgtm!
can we add some TODOs:

• create a way to make EOA.upgrade reachable (currently EOA flow cannot call upgrade)
• create a way to make EOA.upgrade opinionated on target implementations it can upgrade to (some security on interfaces) -> low prio

[bajpai244]

lgtm! can we add some TODOs:

• create a way to make EOA.upgrade reachable (currently EOA flow cannot call upgrade)
• create a way to make EOA.upgrade opinionated on target implementations it can upgrade to (some security on interfaces) -> low prio

@Eikix have added the TODO via this commit.

[Eikix]

one question

[Eikix]

lgtm, will let @enitrat have a quick look

[Eikix]

lgtm

[Eikix]

Nvm approved but you were cursed with the scarb fmt --check fail;D
This happens all too often, should we create a pre-push commit hook?:))

[Eikix]

lgtm

[Eikix]

Nvm, failing CI:)

[enitrat]

@bajpai244 you need to re-compute the expected starknet address, as the class hash has changed

[Eikix]

@bajpai244 you need to re-compute the expected starknet address, as the class hash has changed

Which class hash?

[enitrat]

@bajpai244 you need to re-compute the expected starknet address, as the class hash has changed

Which class hash?

EOA class hash

[Eikix]

lord stop trolling me pls