User events endpoints

[Cauterization]

Closes #379

[keyan-m]

• Avoid using Schema from effect, Data from LE should suffice
• Deposits should go to MidgardAddresses, but withdrawals must go to Cardano addresses.
• All refund addresses must also be Cardano addresses.

[keyan-m]

Taking a look at examples from effect, it seems a hybrid approach would suit us best. Now that you've trimmed down the payload fields, we can use Schema to avoid all those (body as any) checks.

[keyan-m]

If this field from TxOrderParams is not LE.Address (which is just an alias for string), fix it there too.

[Cauterization]

Sorry, didn't understand that one. This field isn't a string.

[Cauterization]

Nvm, I think I got it

[Cauterization]

Taking a look at examples from effect, it seems a hybrid approach would suit us best. Now that you've trimmed down the payload fields, we can use Schema to avoid all those (body as any) checks.

Adding .setPayload from your example triggers a lot of changes due to incompatibility with our current router implementation. I hope just adding schema and parsing the request body with decodeUnknownEither fits that hybrid approach.