Evaluate strategies for reducing Safe code size

[nlordell]

Both #707 #708 increase the code size of the Safe contract, and it is likely that including fixes for both will result in the full Safe code not fitting in 24K (especially since optimizations are disabled).

This issue captures the work to investigate code reduction tricks in order to squeeze in fixes for the 2 aforementioned PRs.

• Some small code size wins are documented in https://github.com/safe-global/safe-contracts/issues/707#issuecomment-1821021138 - things like:
  1. using uint256 internally of smaller uintNs
  2. using bytes calldata or bytes memory differently
  3. unchecked array access
• Large amounts of bytecode can be moved by extracting view methods to use the StorageAccessible.simulateDelegateCall pattern

Expected Outcome

• Comparing different code reduction strategies to determine the best one (consider things like gas consumption, etc.)
• Reduce code size enough to include both fixes to #707 and #708.