Add structures representing the result for each request method

[LimpidCrypto]

• AccountChannelsResponse

  fields	type	explanation
  account	&str	The owner's account's address
  channels	Vec<PayChannel>	The channels owned by the account
  ledger_index	u36	The index of the ledger that was used to generate this response
  ledger_hash	Option<&str>	The hash of the ledger that was used to generate this response
  validated	Option<bool>	Wether the ledger that was used to generate this response was validated
  limit	Option<u32>	The max limit of how many channels to return
  marker	Option<Maker>	Server-defined value for pagination.

• AccountCurrenciesResponse

  fields	type	explanation
  account	&str	The account's address
  ledger_index	u32	The index of the ledger that was used to generate this response
  receive_currencies	Vec<&str>	The currencies the account can receive
  send_currencies	Vec<&str>	The currencies the account can send
  validated	bool	Wether the ledger that was used to generate this response was validated
  ledger_hash	Option<&str>	The hash of the ledger that was used to generate this response

• AccountInfoResponse

  fields	type	explanation
  account_data	AccountRoot	The AccountRoot ledger object with this account's information, as stored in the ledger.
  signer_lists	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• AccountLinesResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• AccountNftsResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• AccountObjectsResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• AccountOffersResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• AccountTxResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• GatewayBalancesResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• NorippleCheckResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• LedgerResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• LedgerClosedResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• LedgerCurrentResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• LedgerDataResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• LedgerEntryResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• SubmitResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• SubmitMultisignedResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• TransactionEntryResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• TxResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• TxHistoryResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• BookOffersResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• DepositAuthorizedResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• NftBuyOffersResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• NftSellOffersResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• PathFindResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• RipplePathFindResponse

  fields	type	explanation
  ``	``

• ChannelAuthorizeResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• ChannelVerifyResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• SubscribeResponse
  SubscribeResponse should be an enum containing the different stream response types.

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• UnsubscribeResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• FeeResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• ManifestResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• ServerInfoResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  fields	type	explanation
  ---	---	---
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• ClioServerInfoResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• ClioLedgerResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• ClioNftInfoResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• JsonResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• PingResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``

• RandomResponse

  fields	type	explanation
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``
  ``	``