[Story][CL]: Pool Manager Module

[p0mvn]

Background

As a user, I would like to have a unified entrypoint for my swaps regardless of the underlying pool implementation so that I don't need to reason about API complexity

#3041 has advocated for a separate module for concentrated liquidity implementation. As a result, we are planning to have 2 entrypoints depending on the underlying pool used:

• balancer -> entrypoint in gamm
• stableswap -> entrypoint in gamm
• concentrated-liquidity` -> entrypoint in ints own module

Suggested Design

Instead of having separate swap messages for each, we should have a unified entrypoint for swaps. Namely, swap-router module that implements the following messages:

• SwapExactAmountIn
• SwapExactAmountOut

Depending on the underlying pool type swapped against, the swap is routed to the desired module.

Existing SwapExactAmountIn and SwapExactAmountOut messages are removed from gamm message server. However, any keeper logic is preserved.

Tasks

• [CL][Swap Router Module]: implement foundational structure #3049
• [CL][Swap Router Module]: remove swap messages and tests, connect with swap-router #3064
• [CL][Swap Router]: create swap messages #3066
• [CL][Swap Router Module]: refactor simulation hack #3087
• [CL][Swap Router Module]: Pool ID routing  #3097
• [CL][Swap Router Module]: deprecate SwapExactAmountInDefaultSwapFee in gamm #3129
• [CL][Swap Router Module]: test CreatePool #3236
• [CL][Swap Router Module]: define InitGenesis and ExportGenesis tests on the suite #3237
• [CL][Swap Router Module]: implement store index to map pool id to swap module  #3238
• [CL][Swap Router Module]: rename the module #3241
• test(x/gamm): InitializePool #3644
• docs(x/swaprouter): add module spec #3881
• [SwapRouter] misc: Delete duplication of SwapAmountInRoute between gamm module and swap router module #3921

Acceptance Criteria

• new module is implemented
• folder structure similar to twap is used
• test coverage is maximized

[mattverse]

Closed by #3051

[p0mvn]

Reopening since we decided to implemented the swap-router component only (not the pool creation logic)

[p0mvn]

Swaprouter was renamed to pool manager, renaming the issue as well

[p0mvn]

I'm going to move the last issue here to #3030 and close this