_**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?**
Reserve RESET_REAPPLY_EXCLUDE_TYPE_CANCEL_REQUEST option.

<!-- Tell your future self why have you made these changes -->
**Why?**
Cancel request should be reapplied only in conflict resolution case.
There is no option to exclude it for reset.

<!-- Are there any breaking changes on binary or code level? -->
**Breaking changes**

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

---------

Co-authored-by: Chad Retz <[email protected]>

**What changed?**

Add a `Failure` field to:
- QueryFailedFailure
- WorkflowQueryResult
- RespondQueryTaskCompletedRequest

**Why?**

Support encoding failure attributes for E2E encryption of messages and
stack traces.

**Server PR**

Coming soon but I've already validated this change locally.

_**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 new structure -WorkflowExecutionExtendedInfo

That structure has few fields:
* execution timeout time
* run timeout time
* last reset time
* cancel requested

(the last one from temporalio/api#339)

<!-- Tell your future self why have you made these changes -->
**Why?**
Per customer request.
Execution timeout timestamp may change after workflow reset, and in this
case customers have no idea when it will fire.
WorkflowExecutionInfo is reused in other server calls, like
ListWorkflow, etc.
Because of that we either add any new field to ES, or it will be nil
which is bad user experience.

<!-- Are there any breaking changes on binary or code level? -->
**Breaking changes**
No

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

Co-authored-by: Spencer Judge <[email protected]>

…n (#508)

_**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?**
Adds a GitHub Actions workflow to automate the process of pushing
protocol buffers to the Buf registry on every push to the main branch.

We need to set the `BUF_TOKEN` secret before merging this PR.

<!-- Tell your future self why have you made these changes -->
**Why?**
We want to be able to depend on server protos from other repositories
(e.g. api-cloud) using the buf package manager.

<!-- Are there any breaking changes on binary or code level? -->
**Breaking changes**
None.

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