Bug: Transaction-related errors are not consistently surfaced to consuming applications

### Describe the bug and the steps to reproduce it

1. Go to a project that uses OnchainKit transaction functionality (or create a minimal app that triggers a transaction using OnchainKit).

2. Connect a wallet using the OnchainKit wallet/connect component.

3. Navigate to the screen/button that triggers an onchain transaction (e.g., “Send”, “Swap”, “Mint”, or any custom “Submit transaction” action wired to OnchainKit).

4. Click the button to submit the transaction.

5. Force a failure case (pick one):

- Use an address with insufficient funds, then submit the transaction, or

- Set an invalid/unstable RPC endpoint and submit, or

- Trigger a known revert condition in the contract call.

6. Observe the app UI and developer console.

7. See that the application does not consistently receive a structured/descriptive error (the error may be generic, missing context, or only visible in the console).

### What's the expected behavior?

Transaction failures should always be propagated to the application in a consistent and structured format. The error should clearly indicate the reason for the failure and include enough context for developers to handle the error programmatically and display meaningful feedback to the user.

### What version of the libraries are you using?

_No response_