Support full, structured failures for queries

[cretz]

Describe the solution you'd like

Today we only support a single string for query failure: https://github.com/temporalio/api/blob/c5bab058fa7ffb52c7137cdbaabd37ac0c41537f/temporal/api/query/v1/message.proto#L56. This means users can't get stack traces or set any of the details they expect to be able to set when using errors in other parts of the platform (workflows, activities, updates, etc). Also, users expect to be able to "encode" failures (i.e. move the message to a payload so it is encryptable, see here), but queries not supporting our proper failure structures does not allow them to do this for queries.

Support a full temporal.api.failure.v1.Failure on query result (can be mutually exclusive with the string today)

[cretz]

Proposed API:

• Add temporal.api.failure.v1.Failure failure to temporal.api.query.v1.WorkflowQueryResult. This will be set by SDKs in addition to the existing error_message.
• Add temporal.api.failure.v1.Failure failure to temporal.api.errordetails.v1.QueryFailedFailure. This will be populated by server with the failure from above