🔀 Path payments within SDEX

[JFWooten4]

What problem does your feature solve?

Path payments are presently specified thinly, not accounting for material details integrated into the protocol.

Moreover, the existing documentation has no code examples. 👩‍💻

Lastly, it doesn't explain the hop limit.

What would you like to see? 📁

In consortium with #763, I propose moving path payments under the SDEX family of documentation.

At least today, path payments are primarily used for arbitrage trading over transfers.

Accordingly, it makes sense to move the op to documentation about liquidity. ♒

What alternatives are there?

We could leave path payments under transactions-specialized and improve the documentation.

This could look like new figures explaining path payments, codified demos, and new cross-referencing.

These additions would chiefly point the user to the SDEX sections which fundamentally power path payments. 💱

[JFWooten4]

This should really get integrated into a more organized SDEX section:

SDEX
├── Liquidity
│   ├── Generalized Liquidity
│   │   ├── Cross-Border Asset Markets
│   │   └── Multi-Currency Liquidity
│   └── Market Depth
├── Order Book
│   ├── Bids
│   └── Asks
├── AMMs (Automated Market Makers)
│   ├── Constant Product AMMs
│   └── Pool Shares
├── Path Payments
│   ├── Source Asset
│   └── Destination Asset
└── Soroban (Smart Contracts)
    ├── Trade Matching
    └── Liquidity Program Execution

[JFWooten4]

The path payments page should also have a section specifically implicating the custody permissions required (and not so for hop assets) re issuing trustlines and account multisig.