feat: Gateway wallet management & bot orchestration improvements

[fengtality]

Summary

• Issue Missing deploy-v2-script endpoint after PR refactoring #129: Restore missing POST /bot-orchestration/deploy-v2-script endpoint with V2ScriptDeployment model
• Issue Add endpoint for setting default Gateway wallet #124: Add set_default parameter to wallet endpoints and new set-default endpoint
• Fix Gateway placeholder wallet addresses causing errors during balance fetching
• Add explicit operation IDs to gateway proxy routes (fixes OpenAPI generation)
• Enable CLMM add/remove liquidity endpoints
• Remove debug prints from main.py

API Changes

New Endpoints

• POST /bot-orchestration/deploy-v2-script - Deploy a V2 script bot
• POST /accounts/gateway/wallet/set-default - Set default wallet for a chain

Modified Models

• GatewayWalletCredential: Added set_default (default: true), removed unused network field
• V2ScriptDeployment: New model for script deployment

Test Plan for QA

Prerequisites

• Gateway running on port 15888
• Valid Ethereum private key for testing

Wallet Endpoint Tests

1. List wallets

   curl -u admin:admin http://localhost:8000/accounts/gateway/wallets

2. Create new wallet

   curl -u admin:admin -X POST http://localhost:8000/gateway/wallets/create \
     -H "Content-Type: application/json" \
     -d '{"chain": "ethereum", "set_default": true}'

   Expected: Returns {"address": "0x...", "chain": "ethereum"}

3. Add existing wallet

   curl -u admin:admin -X POST http://localhost:8000/accounts/gateway/add-wallet \
     -H "Content-Type: application/json" \
     -d '{"chain": "ethereum", "private_key": "0x...", "set_default": false}'

   Expected: Returns {"address": "0x..."}

4. Set default wallet

   curl -u admin:admin -X POST http://localhost:8000/accounts/gateway/wallet/set-default \
     -H "Content-Type: application/json" \
     -d '{"chain": "ethereum", "address": "<address-from-step-3>"}'

   Expected: Returns {"success": true, "message": "Set ... as default wallet for ethereum", ...}

5. Show private key

   curl -u admin:admin -X POST http://localhost:8000/gateway/wallets/show-private-key \
     -H "Content-Type: application/json" \
     -d '{"chain": "ethereum", "address": "<address>", "passphrase": "a"}'

   Expected: Returns {"address": "...", "chain": "ethereum", "privateKey": "0x..."}

6. Delete wallet

   curl -u admin:admin -X DELETE "http://localhost:8000/accounts/gateway/ethereum/<address>"

   Expected: Returns {"success": true, "message": "Successfully removed ethereum wallet"}

Bot Orchestration Test

7. Verify deploy-v2-script endpoint exists

   curl -u admin:admin http://localhost:8000/openapi.json | grep deploy-v2-script

   Expected: Endpoint appears in OpenAPI spec

Gateway Proxy Test

8. Verify gateway proxy works

   curl -u admin:admin http://localhost:8000/gateway-proxy/wallet

   Expected: Returns wallet list from Gateway

Placeholder Wallet Test

9. Verify no errors for placeholder wallets
   • Configure Gateway with defaultWallet: '<ethereum-wallet-address>' (template default)
   • Start API server
   • Check logs for absence of "Invalid Ethereum address format" errors

🤖 Generated with Claude Code

Closes #129
Closes #124

[rapcmia]

Commit 99aeea7

• Build local docker image and run make deploy ✅
• Deploy gateway successfully using development branch ✅
• Tested wallet routes ✅
  • Lists wallet
  • Create new wallet
  • Add existing wallet
  • Set default wallet
  • Show private key
  • Delete wallet
  • Tested what happens if default wallet gets deleted ❌
    • Other wallets are still the same
    • Default wallet still uses the deleted wallet
      
      • I think we need to clear the default wallet or
      • Create a fallback where it will automatically select any of the remaining wallets?
• Verify deploy-v2-script endpoint exists ✅
  • deploy a fake-script.yml and successfully deployed
  • expected results return non existing file from bots/conf/scripts
• Verify gateway proxy works ✅

  curl -s -u admin:admin 'http://localhost:8000/gateway-proxy/config?namespace=solana' | jq
  {
    "defaultNetwork": "mainnet-beta",
    "defaultWallet": "<solana-wallet-address>",
    "defaultNetworks": [
      "mainnet-beta"
    ],
    "rpcProvider": "url"
  }
  logs: INFO:     172.18.0.1:53396 - "GET /gateway-proxy/config?namespace=solana HTTP/1.1" 200 OK
  

• Verify no errors for placeholder wallets ✅
  • Manually setup defaultWallet: '<ethereum-wallet-address>’ from ./gateway-files/conf/chains/ethereum.yml
  • Start hummingbot-api using make deploy
  • No found error related to invalid ethereum address

[fengtality]

tested what happens if default wallet gets deleted ❌
Other wallets are still the same
Default wallet still uses the deleted wallet
image.png (view on web)
I think we need to clear the default wallet or
Create a fallback where it will automatically select any of the remaining wallets?

@rapcmia I will improve Gateway's delete wallet endpoint to clear the defaultWallet. That will be cleaner.

[cardosofede]

LGTM!