fix(token-analyzer): handle USDT-style approve without bool return in token analyzer

[mev15]

Problem

The eth_call token analyzer misclassifies USDT (and any token whose approve() omits the bool return) as Bad. Forwarder.forwardApprove used a typed call IERC20(token).approve(...), which requires a 32-byte bool return. USDT's approve() returns no data, so ABI decoding reverts; the Analyzer's try/catch sets approvalOk = false and the token is reported Bad ("Approval of U256::MAX failed"). forwardTransfer already used a low-level call for this exact reason — only forwardApprove was inconsistent.

Fix

• forwardApprove: use a low-level call that tolerates an empty return, mirroring forwardTransfer.
• Recompile the Forwarder runtime bytecode and update FORWARDER_BYTECODE (solc 0.8.34 --bin-runtime --via-ir --optimize --optimize-runs 200 --no-cbor-metadata --evm-version berlin, matching the documented build in bytecode.rs).
• Add a USDT integration test.

Verification

Before the fix the new test fails at the approve step:

test_detect_impl_usdt ... FAILED
< Bad { reason: "Approval of U256::MAX failed" }
> Good

After the fix it passes; USDC/WETH analysis is unchanged. forge-recompiled bytecode matches the committed FORWARDER_BYTECODE byte-for-byte.

🤖 Generated with Claude Code