Add payable MacroForwarder as trusted forwarder

[d10r]

Rationale

We recently introduced the first Macro Forwarder, see #2014.
When developing Macro contracts, the need for the Macro Forwarder to be payable came up. By leveraging the already existing support of forwarding native tokens via batch operations, this makes it possible to have actions using native tokens.
The PR for the change is #2025

Operations

Deployment is done using the script deploy-macro-forwarder.sh, using a dedicated deployer account (0x0A82D1c074d8266632548cf53477408DB9DBFB29) which yields contract address 0xFD0268E33111565dE546af2675351A4b1587F89F for nonce 0.
The deployer account for this vanity address was found using the application vanity-eth:

vanityeth -i fd02 --contract

Steps executed:

• deploy the contract using the more generic helper script deploy-deterministically.sh
• verify the contract
• register in the Resolver
• create gov action for enabling as trusted forwarder