Test Argent account support

[FabijanC]

Usage related changes

• None

Development related changes

• Add Argent account testing
  • by relying on forking, as per Mention forking in account class selection docs #477
  • only tests interaction with a Cairo1 contract (Cairo0 seems to not work)
• The majority of line changes is just refactoring of account testing
  • continuation of Improve account class testing #476
• Extract some constants (related to forking and account class hash)
• Define OZ and Argent account deployment utility functions
• Removed functions that extracted common functionality because the common functionality was no longer substantial; the new look is more explicit IMO:
  • can_deploy_new_account_test_body
  • can_declare_deploy_invoke_using_predeployed_test_body

Checklist:

• Checked out the contribution guidelines
• Applied formatting - ./scripts/format.sh
• No linter errors - ./scripts/clippy_check.sh
• No unused dependencies - ./scripts/check_unused_deps.sh
• No spelling errors - ./scripts/check_spelling.sh
• Performed code self-review
• Rebased to the latest commit of the target branch (or merged it into my branch)
• Updated the docs if needed - ./website/README.md
• Linked the issues resolvable by this PR - linking info
• Updated the tests if needed; all passing - execution info

[mikiw]

We have OZ account artefact built in devnet and we don't need to fork anything to test it and play with it but now to test Argent account we need to fork mainnet.

Shouldn't we just add an Argent account the same way we added OZ account so devnet users can use Argent account straight away?

[mikiw]

We have OZ account artefact built in devnet and we don't need to fork anything to test it and play with it but now to test Argent account we need to fork mainnet.

Shouldn't we just add an Argent account the same way we added OZ account so devnet users can use Argent account straight away?

ok, since forking is our way to solve it it's ok