[VS Incentives]: Update queries to handle group gauges

[AlpinYukseloglu]

Background

Since group gauges utilize the pool's internal perpetual gauge, is internal/external incentive queries to accommodate the fact that external incentives might route through the pool's internal gauges. This might be slightly hairy to do depending on what the flow we need to accommodate is.

Note on the decision to route through internal gauges: the original design of having external gauges create completely independent gauges unfortunately introduces some complications when gauges distribute to many gauges/pools. We could potentially create a second set of internal gauges to simplify query complexity, but we would need to go back and create these for all existing pools in upgrade handler.

Suggested Design

List of queries to implement:

• all groups
• all group gauges
• all 1:1 mapped groups and group gauges packaged together
• group by group gauge ID
• volume for a given pool

Confirm that the following continue to function correctly:

• /osmosis/pool-incentives/v1beta1/external_incentive_gauges
• /osmosis/pool-incentives/v1beta1/incentivized_pools
• /osmosis/pool-incentives/v1beta1/distr_info
• /osmosis/pool-incentives/v1beta1/gauge-ids/${poolId}
• osmosis/incentives/v1beta1/gauges

Acceptance Criteria

• Frontend's query needs are met
• Old queries hold their invariants
• New queries implemented