Description

Instead of ignoring unknown proto types during statusDetails decoding, this change introduces custom errors wrapped in an Any proto. This allows clients with knowledge of the specific custom error type to decode it.
More information in go/custom-error-details-in-node-rpc.

Impact

Support custom errors instead of ignoring them.

Testing

Added tests here and tested with internal instructions for custom errors.

Checklist

• [ x] Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• [ x] Ensure the tests and linter pass
• [ x] Code coverage does not decrease
• Appropriate docs were updated
• [ x] Appropriate comments were added, particularly in complex areas or places that require background
• [ x] No new warnings or issues will be generated from this change