fix: use correct T3 authorizeKey ABI in tempo-check.sh (#390)

The KeyRestrictions struct was updated after the initial T3 fix:
- TokenLimit gained a `period` field: (address,uint256) -> (address,uint256,uint64)
- CallScope uses nested SelectorRule: (address,bytes4) -> (address,(bytes4,address[])[])

This caused UnknownFunctionSelector(0x19f191e2) because the selector
didn't match the node's IAccountKeychain interface.


Amp-Thread-ID: https://ampcode.com/threads/T-019d52c5-e6ee-73ed-a0f8-86bdf3167745

Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com>

Author: decofe

.github/scripts/tempo-check.sh

@@ -173,8 +173,12 @@ if [[ "$HARDFORK" == "T2" ]]; then
     --private-key "$PK"
 else
   # TIP-1011 (T3+): authorizeKey takes a KeyRestrictions struct
+  # KeyRestrictions = (uint64 expiry, bool enforceLimits, TokenLimit[] limits, bool allowAnyCalls, CallScope[] allowedCalls)
+  # TokenLimit = (address token, uint256 amount, uint64 period)
+  # CallScope = (address target, SelectorRule[] selectorRules)
+  # SelectorRule = (bytes4 selector, address[] recipients)
   cast send --rpc-url "$ETH_RPC_URL" 0xAAAAAAAA00000000000000000000000000000000 \
-    'authorizeKey(address,uint8,(uint64,bool,(address,uint256)[],bool,(address,bytes4)[]))' \
+    'authorizeKey(address,uint8,(uint64,bool,(address,uint256,uint64)[],bool,(address,(bytes4,address[])[])[])) ' \
     "$ACCESS_KEY_ADDR" 0 "(1893456000,false,[],true,[])" \
     --private-key "$PK"
 fi