Feature: Mark assembly blocks as memory-safe

[mmv08]

This PR:

• Fixes Enabling yul optimizer and viaIR causes stack too deep error using Solidity 0.8.19 #544 by marking most of the assembly block memory safe
• Some of the assembly blocks had to be adjusted, such as FallbackManager and StorageAccessible
• Some non-safe blocks, like the forwarded delegatecall in proxy, were left as is

Note:
The tests where we expect a certain return value fail with 0.8.x due to Hardhat being unable to parse the error message. The tests pass fine with 0.76.

[coveralls]

Pull Request Test Coverage Report for Build 5346514267

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 94.2%

---

Totals
Change from base Build 5292680041:	0.0%
Covered Lines:	315
Relevant Lines:	330

---

💛 - Coveralls

[rmeissner]

Do we know if this increases the gas usage?

[mmv08]

Tested it on this test:

        it.only("sends along msg.sender on simple call", async () => {
            const { safe, mirror } = await setupWithTemplate();
            // Setup Safe
            await safe.setup([user1.address, user2.address], 1, AddressZero, "0x", mirror.address, AddressZero, 0, AddressZero);

            const tx = {
                to: safe.address,
                data: mirror.interface.encodeFunctionData("lookAtMe"),
            };
            // Check that mock works as handler
            const response = await user1.call(tx);
            expect(response).to.be.eq(
                "0x" +
                    "0000000000000000000000000000000000000000000000000000000000000020" +
                    "0000000000000000000000000000000000000000000000000000000000000018" +
                    "7f8dc53c" +
                    user1.address.slice(2).toLowerCase() +
                    "0000000000000000",
            );
            console.log(`Gas used: ${await user1.estimateGas(tx)}`);
        });

0.7.6, no optimiser, no allocation: 31940

0.7.6, no optimiser, with allocation: 32160

0.8.19, 1m optimiser runs, no allocation: can’t compile
0.8.19, 1m optimiser runs, with allocation: 32527


[mmv08]

So yes, it does increase the gas used

[rmeissner]

Could we align the variable names withe the other section where we have this code?

[mmv08]

Adjusted

[github-actions]

CLA Assistant Lite bot:
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

1 out of 2 committers have signed the CLA.
✅ @mmv08
❌ @mikhail Mikheev
Mikhail Mikheev seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You can retrigger this bot by commenting recheck in this Pull Request}