AP-743: Deployment Script: Logging of TX Hashes

[0xNeshi]

Explanation of the solution

• created helper functions deploy and deployBehindProxy that wrap common deployment logic (see utils/deploy.ts) which includes logging of Tx hashes only on failed transactions (to avoid cluttering the logs); successful Tx hashes, if necessary, can be found by searching etherscan-like explorers with the deployed contract's address
• moved env.config.ts to config/* folder (+ removed redundant dotenv.config(...) call)
• moved types into a new root folder types/* and updated tsconfig.json to load this folder together with hardhat.config.ts
  Explanation: if types are part of the utils/* folder, then in order for hardhat.config.ts to load config/* (to use CONFIG constant) which imports an enum type from this utils/types/* folder, it (hardhat.config.ts) needs to also load the utils/* folder. This becomes a problem if we have any file inside utils/* use the auto-generated typechain-types folder, since at the time of hardhat.config.ts being loaded these typechain types do not exist (they are loaded afterwards); we cannot guarantee typechain-types won't be used inside utils/* (and it is used with the newly created helper funcs), so updated the code to avoid this issue altogether.
  NOTE: even if these helpers weren't created and the "typechain-types loading problem" didn't occur up 'till now, it would've probably occurred at some later point, so better to tackle it now than later

Instructions on making this work

• run yarn or yarn install to install npm dependencies

[linear]

AP-743 Deployment Script: Logging of TX Hashes

Deploy logic lacks the deployment Tx hash logging (makes it harder to debug)

[stevieraykatz]

Good catch on the fact that the types imported from utils which imported from typechain which could case circular/undefined imports!