Include response payload in gRPC error responses

**As a** blockchain application developer
**I want** my client application to receive payloads returned by chaincode error responses
**So that** I can pass metadata from the chaincode back to the client in the event of a failure

Currently only the error response message text is passed back as part of the gRPC status error message. The Gateway does associate ErrorDetails with this gRPC status error, so perhaps these details could be extended (or additional error metadata added) to include the payload.

It should be noted that using the error payload is not a very common pattern and is not supported by some of the older SDKs.

Start by reviewing how the Gateway associates ErrorDetails with gRPC status errors and where chaincode error responses are converted into client errors. Define done as making the returned error payload available to clients while preserving the existing error message and considering compatibility with older SDKs.

Written by the indexing model from the issue text.