[Bug]: EstimateAMMBounds API doesn't not match up with the state of actual AMM's on stagnet.

[wwestgarth]

Problem encountered

Taking an AMM currently active on stagnet and passing its definition through the EstimateAMMBounds API shows that the AMM's position is outside of the max/min position reported by the API.

My hunch is that the API is wrong, and it is not taking into account the market's price/position decimals.

Observed behaviour

The EstimateAMMBounds API does not reflect real life.

Expected behaviour

The EstimateAMMBounds API returns correct results.

Steps to reproduce

1. Submit `xyz` transaction
2. With this payload
3. Query `abc` API
4. Observe the error

Software version

develop

Failing test

No response

Jenkins run

No response

Configuration used

No response

Relevant log output

No response