fix(eth): propagate structured EIP-1559 fee errors

[shamardy]

This change improves the error handling for EVM withdrawals when the provided EIP-1559 max_fee_per_gas is too low. Previously, the API returned a generic string-based error, forcing the user to guess a new fee. Now, the withdraw endpoint can return a structured error object containing the required network base fee, allowing client applications to better handle the error.

Not all web3 RPC nodes return this detailed information. For nodes that reject the transaction without specifics, a more generic InvalidFee error is returned, indicating that the fee was too low but without providing the required value. In such case, clients should use fee estimator again to get a more up to date value.

Error With Detailed Fee Information

{
  "error": "Invalid fee parameters: Provided gas fee cap is less than the required network base fee.",
  "error_path": "withdraw",
  "error_trace": "coins:3323] ...",
  "error_type": "InvalidFee",
  "error_data": {
    "reason": "Provided gas fee cap is less than the required network base fee.",
    "details": {
      "provided_fee_cap_gwei": "15.0",
      "required_base_fee_gwei": "16.234"
    }
  }
}

Error Without Detailed Fee Information

{
  "error": "Invalid fee parameters: The provided 'max fee per gas' is too low for current network conditions.",
  "error_path": "withdraw",
  "error_trace": "coins:3335] ...",
  "error_type": "InvalidFee",
  "error_data": {
    "reason": "The provided 'max fee per gas' is too low for current network conditions."
  }
}

[dimxy]

LGTM