…ors (#213)

* Support visiting user payloads inside GRPC errors

* Add support for failure visitor

* Only visit payload/failures for multiop and query failures

* Dynamically generate errordetails types to visit

* still process responses when non-status error,

* fix test to actually mutate the underlying payload/failure

* Add message about failure converts coming before payload converters, add parenthesis

* Slice of protoadapt.MessageV1 fixes the type error

<!-- Describe what has changed in this PR -->
**What changed?**
Note:
->[Previous PR we use to
review](https://github.com/temporalio/api/pull/550)<-
It has lots of discussion, and current implementation is mostly what we
settle on. With some changes from design review.

Add definitions for the following API:
* CreateWorkflowRule
* DescribeWorkflowRule
* DeleteWorkflowRule
* ListWorkflowRules

Add definitions for Rules, and Actions.
Corresponding Server PR contains implementation of those APIs.

<!-- Tell your future self why have you made these changes -->
**Why?**
Working on workflow rules.

<!-- Are there any breaking changes on binary or code level? -->
**Breaking changes**
New API is added.

<!-- If this breaks the Server, please provide the Server PR to merge
right after this PR was merged. -->
**Server PR**

[Implementation](temporalio/temporal#7437)

**What changed?**
Added two new history events: `NexusOperationCancelRequestCompleted` and
`NexusOperationCancelRequestFailed`

**Why?**
To support Nexus operation cancellations that should wait only until the
cancellation has been delivered to the handler.

**Breaking changes**
No

**Server PR**

_**READ BEFORE MERGING:** All PRs require approval by both Server AND
SDK teams before merging! This is why the number of required approvals
is "2" and not "1"--two reviewers from the same team is NOT sufficient.
If your PR is not approved by someone in BOTH teams, it may be summarily
reverted._

<!-- Describe what has changed in this PR -->
**What changed?**
Add PAUSED/PAUSE_REQUESTED states to the PendictActivityState enum.

<!-- Tell your future self why have you made these changes -->
**Why?**
To easily differentiate between "activity is paused on server and still
running on worker" and "activity is paused on server and not running on
worker". This is the result of our discussion for activity commands.

In old terms:
"state == PAUSED" is "state = SCHEDULLED and paused_flag = true"
"state == PAUSE_REQUESTED" is "state = STARTED and paused_flag = true"