Various Web3 / AsyncWeb3 objects unnecessarily allocated

[barakman]

Bug Description

• There are various Web3 and AsyncWeb3 objects allocated across the code
• They are mostly identical in their internal configuration, but are nevertheless different instances
• Other than being wasteful, it could lead to some unpredicted erroneous behavior in the system
• For example, injecting the middleware (when needed) might be applied only for some of them

General Solution

• Use a single Web3 object (or possibly two objects, with one of them serving Tenderly in specific)
• Use a single AsyncWeb3 object (or possibly two objects, with one of them serving Tenderly in specific)
• Align the related naming convention - either web3 or w3, but not both of these names in different places