EFTCLIENT-5390 Add MOTO no-reader endpoints to Cloud API REST documentation

[ecunado]

Add documentation for the new MOTO (Mail Order / Telephone Order) operations without reader in the Cloud API REST docs.

Changes

• Add “MOTO Operations (no reader)” section in restendpoints.md:
  • POST /moto/sale – MOTO sale using cardToken.
  • POST /moto/refund – refund linked to a previous operation via originalGuid.
  • POST /moto/reversal – reversal/void linked via originalGuid.
• Clarify that these endpoints:
  • Don’t require serial_number / terminal_type.
  • Don’t accept raw card data (PAN/CVV/expiry).
  • Rely on cardToken and originalGuid instead.
• Add Moto objects in restobjects.md:
  • MotoSaleRequest, MotoRefundRequest, MotoReversalRequest.
  • MotoTransactionResponse (for motoSaleResponse, motoRefundResponse, motoReversalResponse).
• Link endpoints to their corresponding object definitions and remove any mention of internal components (e.g. “Viscus”).

How to test

See comments section in E2E testing + documentation for batching and MOTO endpoints

• Build docs locally and check that:
  • The MOTO Operations (no reader) section renders correctly.
  • Links to Moto*Request and MotoTransactionResponse anchors in restobjects.md work as expected.