Add all 4 transaction IDs for EVM Chain Swaps

[TaprootFreak]

Summary

• Integrate Ponder-Claim database to fetch claim TX hashes for EVM Chain Swaps
• Add ponder PostgreSQL connection pool configuration alongside existing Boltz DB
• Extend SwapDto with cryptographic details (preimageHash, preimage, version)
• Add chain ID fields for source/destination chains
• Add sourceClaimTxId and destClaimTxId fields populated from Ponder-Claim DB
• Create chain ID mapping utility (SYMBOL_TO_CHAIN_ID) for symbol resolution

Changes

• .env.example: Add Ponder PostgreSQL configuration variables
• src/config/config.ts: Add ponderPostgres configuration
• src/subdomains/support/constants/chain-ids.ts: New chain ID mapping utility
• src/subdomains/support/dto/swap-stats.dto.ts: Extended SwapDto with new fields
• src/subdomains/support/services/support.service.ts:
  • Add ponder pool management
  • Add fetchClaimTxsWithChainFromPonder() method
  • Enrich chain swaps with claim TX data

How It Works

1. Fetch chain swaps from Boltz DB (includes lockup TXs)
2. Extract preimageHashes from all swaps
3. Query Ponder-Claim DB's lockups table for matching claim TXs
4. Match claim TXs to swaps using chainId (source vs destination)
5. Return enriched swap data with all 4 TX IDs

Test plan

• Verify Ponder DB connection works when configured
• Test swap endpoint returns claim TXs when available
• Verify graceful fallback when Ponder DB not configured
• Check chain ID mapping for all supported symbols

Closes #121