Promote SDK to beta status (0.5.14): swap RFQ defects fixed, error info surfaced

[ngurmen]

Summary

This branch carries the 0.5.14 release: it hardens the swap (RFQ) path end-to-end after extensive mainnet testing through a bot consumer, quiets known-noisy init logs, surfaces meaningful error information on failed swaps, and promotes the SDK from alpha to beta maturity.

Beta Justification

• CLOB surface: long-running Fuji testnet exposure across orders, deposits/withdrawals, market data, and websocket subscriptions.
• Swap (RFQ) surface: previously untested at the application layer because Dexalot has no testnet RFQ infra. This branch closes that gap with six successful mainnet AVAX/USDC swaps, fixing every defect surfaced along the way.
• Quality: 872 unit tests, 100% line coverage on core/swap.py and core/base.py, mypy clean, ruff clean, no # type: ignore / # noqa.

The pre-1.0 SemVer caveat stays — `Please Note: The public interface may undergo breaking changes` remains in the README.

Changes (chronological)

Commit	What it does
`03d0123`	fix(swap): rewrite quote transformation to match the documented flat `{order, signature, tx}` shape (drop `secureQuote` envelope), unwrap `{success, quote}` envelope, normalize `chain_id`/`quote_id` aliases. `_to_int` helper for hex/decimal/None coercion on `nonceAndMeta`. `_compute_msg_value` for native-asset sells. `_get_rfq_contract(chain_id)` resolves to the connected chain's provider rather than always Dexalot L1. Contract address checksumming via `Web3.to_checksum_address`.
`0a8ef98`	doc(README): update RFQ Quotes API documentation.
`474d7ec`	chore(release): bump version to 0.5.14.
`460414e`	fix(base): demote rfq_pairs HTTP 4xx to debug — chains without an RFQ deployment (e.g. Ethereum) used to log a warning on every `initialize_client`.
`97a854b`	fix(base): extend the demotion to all non-200 paths — the Dexalot RFQ endpoint actually returns 500 for unsupported chains. `_fetch_rfq_pairs` is best-effort at init; real failures surface from the trade-time call.
`b1f6b51`	fix(swap): `execute_rfq_swap` failures now return `Transaction reverted: tx=0x..., block=N, reason=RF-XXX-NN`. New `_extract_revert_reason` helper replays the failing tx as `eth_call` against the failing block to recover the on-chain revert string.
`5686dbd`	chore(release): promote PyPI trove classifier and README copy from alpha to beta.

Test plan

• `make test` — 872 unit tests pass
• `make cov` — 100% coverage on the modified files (`core/swap.py`, `core/base.py`)
• `make lint` — clean
• `make mypy` — clean
• Mainnet RFQ swap: six successful trades from `trade_bots` against Avalanche C-Chain (`0x8d7401`, `0x9f6b4f`, `0x9bfe44`, `0x16506122`, `0x1db59188`, `0x04cfc77b`).
• Reverted swap: surfaced revert reason via `_extract_revert_reason` on the one transient revert observed during testing.
• Init logs: confirmed `Rfq Pairs Fetch Failed` is no longer emitted on `initialize_client` calls in production.

Upgrade notes

• Callers that consumed firm-quote responses as `{secure_quote: {...}}` need to read the flat top-level `order`/`signature`/`tx` keys directly (matches the documented API).
• `execute_rfq_swap` failure messages now include `tx=...`, `block=...`, and (when available) `reason=...`. Code that string-matches on the literal `Transaction reverted` prefix still works; consumers can additionally parse the new fields for debugging.