Validate/bound max liquidity per tick

[kadenzipfel]

Uniswap has a max liquidity per tick given the tickSpacing used. It can be retrieved with Pool.tickSpacingToMaxLiquidityPerTick. It's important that we never attempt to provide liquidity, or even compute liquidity amounts, e.g. with getLiquidityForAmount0/1 if we exceed the max liquidity per tick.

We should consider all the places where we must validate the liquidity per tick is less than the max amount and if it is not less, we should extend the slug ranges accordingly

Alternatively, it may be possible to derive whether we will ever reach this maximum given the constructor parameters and enforce this there

[kadenzipfel]

Haven't had the time to complete this but here are some options I've been exploring:

1. We can enforce that given the numTokensToSell and maximum price (likely computed as a function of startingTick and gamma), the maximum amount of liquidity remains less than the tickSpacingToMaxLiquidityPerTick(tickSpacing). Something I'm unsure of with this is whether it's possible to have a higher amount of liquidity in the numeraire token towards the end of the sale. I suspect there's a relationship between numTokensToSell and price that we can depend on, but I'm not certain on the math yet. This can all be enforced in the constructor
2. Similarly to above, instead of triggering a revert in the constructor, we can document that if the numTokensToSell or maximum expected proceeds exceeds some precomputed amount, then a tickSpacing > 1 must be used. We can clarify the maximum amounts that can be used with different tickSpacings. I'm not sure yet how to compute this maximum amount
3. When we compute the amount of liquidity to provide in each slug, we can check whether that amount of liquidity exceeds the maximum for the given tickSpacing and tick range used. We can then adjust the tick range such that the maximum is no longer exceeded. I'm a bit concerned that this strategy will result in unexpected behavior with the bonding curve. We also have to carefully consider how to modify the tick range