AMM enforce minimum liquidity by wrapping addPool with a new contract

[Chris-Hibbert]

What is the Problem Being Solved?

When we enforced minimum liquidity inside addPool (#5377)

• the AMM had to learn about the Reserve
• the AMM had to handle errors while creating the pool and notifying the Reserve
• Races were introduced (Under load, brands do not match #5571)

Description of the Design

• move addPool() to the creator facet
• write a new contract that enforces the minimum and transfers liquidity tokens to the reserve

Security Considerations

Simplify the interface and reduce error conditions.
If there's an issue in creating the Reserve pool, the AMM remains in a consistent state.

Test Plan

check for races

[Chris-Hibbert]

The AMM was removed in #7074