`distribute()` calls

[stas]

Every midnight on Wednesday to Thursday we have two hours, one before and one after that are reserved for the protocol maintenance operations.

During this time we need to call distribute() on every gauge we have registered:
https://github.com/velodrome-finance/contracts/blob/main/contracts/interfaces/IVoter.sol#L139-L142

This needs to scale for whatever is the number of gauges we need to call.

---

If helpful, we can use the Sugar calls as an example how the gauge and pool addresses are fetched:
https://github.com/velodrome-finance/sugar/blob/v3/contracts/LpSugar.vy#L283-L331

Ideally we don't have to depend on Sugar for this automation.

[ethzoomer]

Now that Superchain 1.0 is live, some of the gauges that distribute is called for will be crosschain gauges. The function calls remain the same for these distributes, but in order for the transaction not to revert, tx.origin in the distribute transaction will need to have a WETH balance on OP Mainnet, and have approved WETH to be spent by the MessageBridge at 0xF278761576f45472bdD721EACA19317cE159c011