Improve `starknet-foundry` version for a future complete migration

[jrcarlos2000]

Issue Overview

Currently this branch supports deployment scripts fully written in cairo. It uses Starknet foundry

Some pending TODOs are ( in order of priority ):

• In deploy script, skip contract declaration if it exists, this is a pending fix from snfoundry.
• there are 2 scarb.toml files, since this all use the same versions of cairo and starknet, are we able to have only one scarb.toml, or one single project that has scripts, tests and contracts. This will def have a better UX.
• minimize the usage of this script, its better if we can get rid of it.
  • Idea : Consider exploring the usage of environment variables like in foundry, this will let us have an .env and avoid passing params like --account when running it.
• Currently transactions take long to execute, are we able to either:
  • choose the block tag to be pending by default
  • build the contract deployment transactions , batch them and execute at the end of the script, similar to the current deploy script on main
  • [IMPORTANT] the waiting time is considerably slower compared to scripts in main. In order to have this by default, the speed has to be same or faster.

[oceanlvr]

for issue 1:

In deploy script, skip contract declaration if it exists, this is a pending fix from snfoundry.

it's seems that [Starknet foundry](https://github.com/foundry-rs/starknet-foundry) we use is version 0.27.0

and the latest version is 0.30.0, we could use api like this to skip declare if it have been declared. it's seems that we could not now what if the contract have been declared in 0.27.0.could i upgrade this package? so that i could use this api

https://foundry-rs.github.io/starknet-foundry/appendix/snforge-library/declare.html#declare