test: scarb library with template account contract

[ICavlek]

In scope of this PR, scarb library has been introduced in test environment. Scarb is a tool that is used for compilation of smart contracts within the starknet ecosystem. This is marked as an initial step for actual account deployment within test cases.
General overview of the introduced changes:

• Added two test cases, one for sepolia and one for katana
• Added template account contract
• Possibility to create and compile multiple account contracts

Additional notable changes:

• Refactor of test module
• Added TODOs for additional work

Since the general overview of the test case can be observed with the changes in this PR and future TODOs, please consider the structure and the workflow of the test case within this PR.

[LKozlowski]

LGTM

To make sure I understand it correctly: We use scarb from within tests to compile account's smart contract then deploy it and test it?

[ICavlek]

LGTM

To make sure I understand it correctly: We use scarb from within tests to compile account's smart contract then deploy it and test it?

Yes, scarb is used within the executor. I have created a template where multiple accounts will be deployed on Katana before using the framework on Sepolia. Since the compilation is a slow process (~30 secs in test), it is pushed in separate threads based on the amount of newly deployed accounts.
After that, with starkli introduced also as lib (issue that I am currently working on) we will be able to declare and deploy it on network

[sergey-melnychuk]

LGTM % a few nitpicks

[ICavlek]

@sergey-melnychuk @LKozlowski I have updated PR with significant changes and I would like you to have another look at it. Based on the comments, I have reworked it in a way that I have removed executor.rs and added coordinator.rs which will only handle the environment of the contracts.

One additional thing that is not directly connected to this PR, clippy fails in gen.rs (see workflows on commits). I have updated it here so that it can be observed, but I guess that this will be done in a different PR. I will update it here when it is done.

[sergey-melnychuk]

Left a few comments about unnecessary complications if a very simple workflows (introducing structs with hard-coded unchangeable properties, when all the process can be described as a composition of simple functions).

[ICavlek]

@sergey-melnychuk @LKozlowski Updated PR based on comments:


• Recovered two accidentally deleted tests
• Removed two template tests that will be added in scope of separate PRs
• Removed Compiler class and reduced it to single function
• Removed coordinator.rs, it's Coordinator class and reduced it to single function in utils.rs