[BIP-279] Enable COIL/USDC Gauge 2% Cap Correction [Ethereum]

PRs with Payloads

https://github.com/BalancerMaxis/multisig-ops/pull/168 https://github.com/BalancerMaxis/multisig-ops/pull/169

Summary:

The initial gauge proposal for COIL/USDC passed as BIP-266 here. During the gauge creation process, there was concern regarding a 10% or 2% cap and a mistake occurred where the 2% cap gauge was made incorrectly. It directs to the 10% cap gauge itself, as opposed to the COIL/USDC pool. This oversight in process was caught during the execution* process by the Balancer Maxi team, but initial mistake was made by myself. I am proposing the approval of the gauge remade correctly to be activated, and killing of the current gauge based on the specifications below.

In terms of preventive actions, @Tritium has already made an automated script to check all gauges made in the future as payloads are made for them. How this would have worked if in place prior can be seen here. While this was one of our first mistakes with the gauge creation process, we will do everything in our power to be sure this cannot happen again. We value our partners and ecosystem greatly and want to be sure their experience with us is seamless.

References/Useful links:

For all protocol, governance, and initial specifciation information please reference BIP-266.

Specification:

Part A: The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptor at 0x8F42aDBbA1B16EaAE3BB5754915E0D06059aDd75 and call performAction with the GaugeController at 0xC128468b7Ce63eA702C1f104D55A2566b13D3ABD for the target(address) argument and using 0x3a04f900 followed by the gauge address 0x78a54C8F4eAba82e45cBC20B9454a83CB296e09E and the corresponding gauge type for the data(bytes) argument.

data(bytes) :

0x3a04f90000000000000000000000000078a54c8f4eaba82e45cbc20b9454a83cb296e09e0000000000000000000000000000000000000000000000000000000000000002

Killing Old Gauge

Part B: The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptor at 0x8F42aDBbA1B16EaAE3BB5754915E0D06059aDd75 and call performAction using 0xab8f0945 for the data(bytes) argument and 0x249034A0EA97E76c2b4AB7a1727CBC52548c531c for the target(address) argument.