feat: add gauges to address book

[gosuto-inzasheru]

wip

[gosuto-inzasheru]

@Tritium-VLK i need some feedback here

this pr would inject all preferential gauge addresses for all chains into the address book every weekend (via the cron jobbed transform-deployments.py), together with their symbols. see the diff on addressbook.json for a successful poc

this should help the ci reports label these gauges whenever they occur in a tx, it introduces great searchability for anyone (cmd-f the json), and is a first step in solving BalancerMaxis/multisig-ops#639 (custom reports for injector config payloads)

however, i now realise that there arent any bpt addresses in the address book either! im thinking of doing the same for those.

wdyt?

[gosuto-inzasheru]

hmm we would need to filter the pools query a bit, getting 7k pools currently across all chains!

{
    pools(
        where: {swapEnabled: true}
    ) {
        address
        symbol
    }
}

[gosuto-inzasheru]

note: pools should be written first, so they can be overwritten by deployments

[gosuto-inzasheru]

ok this is good to go; adds pools and gauges to the (reverse) address books

[gosuto-inzasheru]

to run locally, follow the generate_addressbooks.yaml workflow: python gen_pools_and_gauges.py && python transform-deployments.py&& python gen_addresses.py

[Tritium-VLK]

Ok let's try it and keep an eye on things and we can revert the dataset if there are problems. Will merge now, regen everything and then test a bunch of our tooling.

[Tritium-VLK]

It somehow looks here like reverse records are being feed into the non-reverse flatbooks.

[Tritium-VLK]

If this is derived data (not a human input), i'd move these files to outputs.

So you could have like arbitrum_poolinfo.json and include the pools and gauges there/etc. Maybe it makes sense to just roll it all into one file. Let's think about it a bit more. I like the idea that the base flatbook is pretty clean, and the addresses by pool/gauge tend to have a lot of overlap/are more messy.