fix: return submit errors with context information

[arkadiuszos4chain]

Current implementation returns misleading error messages from SubmitTx eg:

2024/02/01 20:08:25 error: server responded with no-success code. details: { statusCode: 404, body: "no results"
 }

which suggests Arc node responded with the error.

Proposed solution formats message and extends error information with context:

2024/02/01 19:55:52 error: SubmitTransaction: submiting failed
        inner error: rawTxRequest: updateUtxoWithMissingData() failed
                inner error: junglebus request failed: server responded with no-success code. details: { statusCode: 404, body: "no results"
 }

Pull Request Checklist

• 📖 I created my PR using provided : CODE_STANDARDS
• 📖 I have read the short Code of Conduct: CODE_OF_CONDUCT
• 🏠 I tested my changes locally.
• ✅ I have provided tests for my changes.
• 📝 I have used conventional commits.
• 📗 I have updated any related documentation.
• 💾 PR was issued based on the Github or Jira issue.

[chris-4chain]

Generally I really like this approach :)

My thoughts:

• I found another place where is might be wrapped as you proposed: function parseArcError.
• I'm only wondering, how the indentations will be parsed/treated by log collecting apps like elasticsearch/kibana.