Wrap RPC errors

[dhaidashenko]

Ticket

• Wrap all RPC related errors to simplify filtering
• Include RPC name into the error to simplify linking to the health checks
• Format SendTxErrorCodes to make CRIT error msg more self explanatory

[github-actions]

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset.

[poopoothegorilla]

do we need to close the unSub chan?

[dhaidashenko]

No, we should not close unSub, as it might cause panic on the callers side if it calls Unsubscribe. Example. There is no guarantee that we won't try writing into unsub, even if done is closed.
Also we are not leaking resources. As soon as subErrorWrapper is closed, we won't have any additional reference to the unsub, so when GC collects subErrorWrapper it will also collect unsub.

[HelloKashif]

@dhaidashenko looks good to me. Just one thing to confirm:
If I want to filter out all RPC related errors I need to exclude messages prefixed with RPCClient returned error... correct?

[github-actions]

I see you added a changeset file but it does not contain a tag. Please edit the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
72.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube