feat: add example Tempo batch tx

[maxime-oe]

Note

Medium Risk
Introduces new transaction-sending UI that can trigger real on-chain ERC20 transfers using a custom tx type and fee token fields. Risk is mainly accidental execution/misconfiguration rather than deep system impact.

Overview
Adds a new “Tempo Transactions” test component that renders inputs for chainId, ERC20 token address, and fee token, plus a button to submit a Tempo type: 0x76 batched eth_sendTransaction with two hardcoded ERC20 transfer calls.

Wires this component into src/index.js so it appears in the app UI and enables/disables it based on the existing globalConnectionChange / disableAndClear events, displaying the resulting tx hash (or error) inline.

^{Written by Cursor Bugbot for commit 5470e68. This will update automatically on new commits. Configure here.}

[seaona]

added a couple of small suggestions. Let me know if they make sense!

[seaona]

for adding a bit more flexibility in the testing side, could we add an input element in the front end, so we can pass our custom ERC20 token address if we wish?
This address could be taken as the default value, if none is provided.
Wdyt?

[seaona]

same to these, maybe if we can choose that from the UI as well, we won't need additional changes later (ie changing the chaind)

[maxime-oe]

@seaona Ok will do a form and use the current values as default to maintain the aspect "one click to test" possible.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

[maxime-oe]

@seaona comments addressed ;)
Simple input texts pre-filled with what were the default values.

[maxime-oe]