feat: use subgraph to pre-populate gauge options for the safe user in ui

[petrovska-petro]

No description provided.

[gosuto-inzasheru]

looks great, works on localhost for me!

seeing the pool name of the gauge and not the address is a great step in ux :)

this does raise a new question; what if we want to enable harvests for both?

and probably also somewhat out of scope, but i noted that even if connected to opti goerli the same gauges show up. so somewhere we should start becoming chain aware. (a subgraph will always be for a single specific chain only, for a different chain a different subgraph will be needed)

[petrovska-petro]

and probably also somewhat out of scope, but i noted that even if connected to opti goerli the same gauges show up. so somewhere we should start becoming chain aware. (a subgraph will always be for a single specific chain only, for a different chain a different subgraph will be needed)

added the chain awareness in 9249a30

[petrovska-petro]

this does raise a new question; what if we want to enable harvests for both?

another item was planning to scope on the ui side is to allow multi-select on the options and to do a multi-call in the safe app to enable both atomically

[gosuto-inzasheru]

i need to refresh after switching chains, in order to refresh the gauge dropdown

maybe open a separate issue for this?

[gosuto-inzasheru]

because the rest lgtm and can be merged imo :)