feat(v4-solana): add support for jito bundles (#329)

[tomiiide]

Why was it implemented this way?

Sync #329 with v4

Adds support for submitting Solana transactions as Jito bundles, enabling MEV-protected atomic transaction execution.

Changes

** Connection -> RPC **

• Replaced the connection nomenclature to rpc

Jito RPC Client

• Created a @solana/kit Jito RPC client with bundle-specific methods:
  • sendBundle - Submit transaction bundles
  • getBundleStatuses - Check bundle confirmation status
  • getTipAccounts - Get Jito tip accounts
  • simulateBundle - Simulate bundle execution
• Extended Jito RPC to include standard Solana RPC methods

RPC Management

• Added RPC registry that automatically detects and categorizes Jito vs standard Solana RPCs
• RPCs are detected by checking support for getTipAccounts method

Bundle Submission

• Implemented sendAndConfirmBundle action that:
  • Submits transaction bundles to multiple Jito RPCs in parallel
  • Polls for bundle confirmation with blockhash expiry handling
  • Returns bundle ID, transaction signatures, and confirmation results

SDK updates

• Added jitoBundle flag to route options - when enabled, step transaction requests include the flag so the API returns Jito-compatible transaction data
• Updated SolanaStepExecutor to handle bundle transactions with proper signing and submission flow

Checklist before requesting a review

• I have performed a self-review and testing of my code.
• This pull request is focused and addresses a single problem.
• If this PR modifies the SDK API or adds new features that require documentation, I have updated the documentation in the public-docs repository.

[tomiiide]

Don't add changes from main to this branch as it contains status manager that breaks the widget.

@chybisov @effie-ms

[tomiiide]

Breaking changes on the widget has been fixed here -> lifinance/widget#649