use the new error in the transactionError subscription

### Is your feature request related to a problem?

_No response_

### Describe the solution you'd like

We deprecated the `reason` from the `transactionError`.
Instead the SDK should use the new property`error` which is of type :
```
{
code: Int
data: any
message: String
}
```

### Additional context

I believe this require a major version bump

A util function such as `formatError` would be great because we might have inception of errors and that would provide great error message (example: "Invalid recipient execution: Condition Failed: still locked")

### Epic

_No response_

Start by locating the transactionError subscription and the current use of its deprecated reason property. Trace the subscription payload to confirm how the new error object is exposed, then check existing tests for transaction errors. Done means the subscription uses error consistently, with any formatError behavior and major-version changes documented or covered by tests.

Written by the indexing model from the issue text.