feat: AfterCosmWasmPoolCreated hook to create an internal gauge

[p0mvn]

Background

Currently, we do not have such hook. As a result, cosmwasm pools cannot be internally incentivized. We would have to create a gauge manually for every such pool

Suggested Design

Implement AfterCosmWasmPoolCreated hook that creates one gauge (similar to Classic pool logic)

Acceptance Criteria

• hook created
• creates gauge
• tested

[mattverse]

@p0mvn You are referring to perpetual gauges correct?

[AlpinYukseloglu]

Floating this up as an important feature to implement for volume-splitting incentives to work with CW pools. We should also not forget to create these internal gauges for existing CW pools (e.g. transmuter) in upgrade handler

[p0mvn]

Let's track this here: #5864

[PaddyMc]

I created a bug report here => #6230

⬆️ maybe the bug can be closed

[p0mvn]

Considering two approaches:

• Lock based approach. In that case, we don't need this distribute_incentives message and instead distribute to locks directly like with balancer. Here, we need the CW pool to mint shares
• NoLock approach that distributes directly to the pool (like CL) and lets the pool handle the incentives in a custom way. For this we would need a custom distribute_icnentives sudo message that would notify the pool about distribution at epoch. However, this sudo message would just be fire and forget without error checking. If an error occurs, it is silently skipped.

[p0mvn]

Tentatively from discussions:

Moving this feature out of upcoming scope until the goals of cw pool incentives are more product-defined

Ref: https://osmosis-network.slack.com/archives/C04LZFBHGQ5/p1695299430819449

Currently, the only cw pool - transmuter does not need incentives.

Some prototyping progress on the NoLock approach: https://github.com/osmosis-labs/osmosis/tree/roman/cw-pool-incentive-progress

[p0mvn]

Adding suggestions and context from Boss:

+1 for implementing once there is a need. I reckon 2nd choice is better for customization but I would rather retain from fire and forget and have something similar to dead-letter queue that could manual retry since distributed incentive might become staled assets on the contract.