[BIP-471] Update LayerZero Configs for Avalanche

PR with Payload: https://github.com/BalancerMaxis/multisig-ops/pull/595

Summary:

The LayerZero team is moving their validation from MPT, to a new featherproof library this is due to the handling of large call data and event sizes across the network. In order for AVAX rewards to properly be streamed in the future Balancer must update the inbound proof library from MPT to feather proof. There also must be a similar update to the outbound mainnet configuration. This will require two transactions handled by the DAO multisigs on each network.

Motivation:

BAL must continue to stream to all of Balancer's supported networks. By making these updates we will be able to continue to do this, in particular in this case for Avalanche.

References:

Version of 0 and configTypes can be confirmed here. chainIds can be confirmed here.

Specifcations:

Ethereum:

• The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the BALProxy 0xE15bCB9E0EA69e6aB9FA080c4c4A5632896298C3 by writing setConfig passing the following arguments: _version: 0 _chainId: 106 for Avalanche _configType: 4 for an outbound proof type _config: 0x0000000000000000000000000000000000000000000000000000000000000002 for featherproof

Avalanche:

• The DAO Multisig 0x17b11FF13e2d7bAb2648182dFD1f1cfa0E4C7cf3 will interact with the BALProxy contract 0xE15bCB9E0EA69e6aB9FA080c4c4A5632896298C3 by writing setConfig passing the following arguments: _version: 0 _chainId: 101 for Ethereum _configType: 1 for an inbound proof library version _config: 0x0000000000000000000000000000000000000000000000000000000000000002 for featherproof