[Certora Audit] G-09. Cache array length outside of loop

[remedcu]

This pull request includes several optimizations to the OwnerManager and ERC165Handler contracts by reducing the number of times array lengths are accessed within loops. These changes aim to improve the efficiency of the code by storing the array lengths in variables before the loops.

If not cached, the solidity compiler will always read the length of the array during each iteration. That is, if it is a storage array, this is an extra sload operation (100 additional extra gas for each iteration except for the first) and if it is a memory array, this is an extra mload operation (3 additional gas for each iteration except for the first).

Optimizations in OwnerManager contract:

• contracts/base/OwnerManager.sol: Stored _owners.length in a variable ownersLength before the loop to avoid repeatedly accessing the array length.
• contracts/base/OwnerManager.sol: Updated ownerCount to use the ownersLength variable instead of accessing _owners.length again.

Optimizations in ERC165Handler contract:

• contracts/handler/extensible/ERC165Handler.sol: Stored handlerWithSelectors.length in a variable len before the loop in addSupportedInterfaceBatch to avoid repeatedly accessing the array length.
• contracts/handler/extensible/ERC165Handler.sol: Stored selectors.length in a variable len before the loop in removeSupportedInterfaceBatch to avoid repeatedly accessing the array length.