Neg Risk Support

[mshrieve]

Modifies the Clob Client in anticipation of the future Neg Risk market type.
Adds a new OrderOptions object:

type OrderOptions = {
  tickSize: TickSize;
  negRisk?: boolean;
}

These modifications do not require extra calls to the CLOB, e.g., to get the exchange address to be used when signing.
Contract addresses are now hard-coded in this repo, as opposed to retrieved from the clob-order-utils.

[poly-rodr]

As the negRisk flag is a param of this function, the frontend (or any other client) has to know in advance if the market is neg risk or not, is that information available in this context or should we add a new CLOB request to resolve that?

cc: @mttwlkr @L-Kov

[mshrieve]

Yes, the frontend will known at the time of calling whether the market is neg-risk or not. We considered adding an extra call to the CLOB to determine locally (to this package) whether the market is neg-risk but opted to make these calls as light-weight as possible.

[poly-rodr]

it makes sense, thanks!