debug_traceTransaction fails with some specific tx hash

[acuarica]

For some transaction hashes, e.g., 0x47797217418d267efc5afbe2a670d1fdfd0a1ad5cc098c014a8ee5386b4243da, the RPC method debug_traceTransaction fails with the following error

Cannot destructure property 'call_type' of 'actionsResponse.actions[0]' as it is undefined.

Steps to Reproduce

$ curl --request POST \
  --url https://testnet.hashio.io/api \
  --header 'content-type: application/json' \
  --data '{ "method": "debug_traceTransaction", "id": 2, "jsonrpc": "2.0", "params": ["0x47797217418d267efc5afbe2a670d1fdfd0a1ad5cc098c014a8ee5386b4243da",{"tracer": "callTracer"}] }'

{"error":{"code":-32603,"message":"[Request ID: f798f652-4ebc-49c5-8ba1-0923ac2ae223] Error invoking RPC: Cannot destructure property 'call_type' of 'actionsResponse.actions[0]' as it is undefined."},"jsonrpc":"2.0","id":2}%

Investigate why this happens and fix the issue.

[quiet-node]

It appears that these transaction hashes do not contain any call trace data — specifically, the /contracts/results/{txHash}/actions endpoint returns an empty array.
For example:

curl -X 'GET' \
  'https://testnet.mirrornode.hedera.com/api/v1/contracts/results/0x47797217418d267efc5afbe2a670d1fdfd0a1ad5cc098c014a8ee5386b4243da/actions?limit=2&order=desc' \
  -H 'accept: application/json'

In such cases, the code currently attempts to deconstruct call_type from the first element of the array ([0]), which is undefined. This leads to the observed error when the code tries to access properties of null or undefined.

To improve robustness, we should enhance the null handling logic for this operation to gracefully handle cases where the actions array is empty.