feat(cadence): support exact-out mode quote via swap

[liobrasil]

Summary

This PR adds an opt-in exact-output mode that works through the existing swap(...) entrypoint, so callers can request exact-out behavior without changing the Swapper.swap signature.

Why

After swapExactOut(...) was added to the interface, apps that still call swap(...) continue to use exact-input semantics.
This change introduces a quote modality so swap(...) can execute exact-out when explicitly requested.

What changed

• Added SwapConnectors.SwapMode (IN / OUT).
• Added SwapConnectors.ModeQuote:
  • extends DeFiActions.Quote
  • includes mode
  • includes leftoverInReceiver capability for returning unused input during exact-out.
• Added helper constructors:
  • SwapConnectors.asModeQuote(...)
  • SwapConnectors.asExactInQuote(...)
  • SwapConnectors.asExactOutQuote(...)
• Updated UniswapV3SwapConnectors.Swapper.swap(...):
  • if quote is ModeQuote + OUT, it executes exact-out internally and deposits leftover input to leftoverInReceiver.
  • default behavior remains exact-input for regular quotes.
• Updated SwapConnectors.MultiSwapper.swap(...) with the same mode-aware exact-out path, routed through the selected inner swapper.
• Updated uniswap_v3_swap_exact_output.cdc to use:
  • swap(...) + SwapConnectors.asExactOutQuote(...)
  • token-in leftover receiver cap derived from token metadata (FTVaultData), not hardcoded paths.

Compatibility

• Backward compatible for current callers using BasicQuote + swap(...).
• Exact-out via swap(...) is opt-in only (through ModeQuote).
• Invalid/missing leftover receiver capability fails explicitly.
• Existing unsupported exact-out routes still fail as before.

Notes

• This PR does not remove swapExactOut(...); it remains available.
• Main intent is to let generic swap(...) flows opt into exact-output semantics safely.

Design context

This approach is based on the quote-modality direction originally suggested by @jribbink in PR #127 discussions:

• s4 improve uniswapv3 swap precision #127 (comment)
• s4 improve uniswapv3 swap precision #127 (comment)

The goal is to keep generic {Swapper} call sites usable while allowing explicit exact-out behavior through quote semantics.