feat(SQS): custom quote query

[p0mvn]

Closes: #XXX

What is the purpose of the change

There are cases where it might be desired to specify a specific query path for quoting. This is especially useful for debugging.

As a result, such query is exposed.

It takes a list of pool IDs. If there is a route that mathes these pool IDs, such route is quotes. Otherwise, an error is returned.

Example:

curl "localhost:9092/custom-quote?tokenIn=5000000uosmo&tokenOutDenom=uion&poolIDs=2" | jq .
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   305  100   305    0     0    309      0 --:--:-- --:--:-- --:--:--   309
{
  "amount_in": {
    "denom": "uosmo",
    "amount": "5000000"
  },
  "amount_out": "8714",
  "route": [
    {
      "pools": [
        {
          "id": 2,
          "type": 0,
          "balances": [],
          "spread_factor": "0.005000000000000000",
          "token_out_denom": "uion",
          "taker_fee": "0.001000000000000000"
        }
      ],
      "out_amount": "8714",
      "in_amount": "5000000"
    }
  ],
  "effective_fee": "0.006000000000000000"
}

Testing and Verifying

Go test added with uion/uosmo

Documentation and Release Note

• Does this pull request introduce a new feature or user-facing behavior changes?
• Changelog entry added to Unreleased section of CHANGELOG.md?

Where is the change documented?

• Specification (x/{module}/README.md)
• Osmosis documentation site
• Code comments?
• N/A

[czarcas7ic]

consider in the future adding length to GetRoutesFromCandidates to prevent having to iterate over them again here

[p0mvn]

I'm note sure what recommendation is exactly. We would have to iterate anyways since we want to make sure each pool's ID matches the id of the given list of pool IDs in the same order

[p0mvn]

Will not be blocking on this, please lmk if any follow-ups are needed