Include the slippage tolerance in the settings of the user when we submit the order

[anxolin]

We want to pass the slippage tolerance value as an order parameter to the API's and/or also to the Sentry.

Original issue gnosis/cowswap#2617 by @nenadV91

[anxolin]

Bringing back the comment from our sprint session:

Coordinate with backend, the initial Idea:

• When we get the quote, backend will send an ID that identififies the quote. This id helps them to debug and we should include it in the posting of the order
• Include slippage in the post i.e in bips? or '0.5' (to agree with backend)
• [good to have] Ideally include this information in the metadata (IPFS)

Depend on cowprotocol/services#131

[anxolin]

Adding some document to help with the definition and coordination https://docs.google.com/document/d/1N8K-ueKxxuuFfKjnegbPUYx30Qk1H8zjeiLo3jg-X14/edit#

[anxolin]

Nick created a task for the quoteId cowprotocol/services#170

[alfetopito]

Implementation details (based on the gdoc shared above)

CowSwap:

1. New field quoteId received as part of the /quote api response
2. Propate/store in the internal state 3 new fields (2 might be there already, need to check)
   • sellAmount
   • buyAmount
   • quoteId
3. Before placing an order, create the appData doc(1)(2)
4. Upload given doc to IPFS
5. Use appData hash in the order as it's already done

4 is non-blocking
For added resilience we could send it to backend endpoint in case upload/pinning fails on client side.
5 can be derived from appData doc without depending on

(1) Need to merge with any potential affiliate link data present. Will likely require a re-work on that flow, though

(2) Requires a model change and probably version bump on metadata doc definition:
Cow-sdk:

1. Add quote metadata (see gdoc with definition)
2. Add related json validation
3. Make sure it's still backwards compatible (we are simply adding a field, no changes for existing fields)
4. Publish new npm package