WorkerDeployments becoming async in nature. (#647)

_**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?**
- Added a monotonically increasing counter which shall be used by the
history service when scheduling workflow/activity tasks.
- Add an enum in the RoutingConfig which shall convey the routing config
propagation status. This shall allow users to have a peek at the exact
stage where an update, scheduled by a worker-versioning write API, has
reached.

<!-- Tell your future self why have you made these changes -->
**Why?**
- The main purpose of this is to resolve out-of-sync history and
matching partitions when it comes to deciding how to route tasks

<!-- Are there any breaking changes on binary or code level? -->
None, just new fields and enums, no new APIs

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

---------

Co-authored-by: Carly de Frondeville <[email protected]>

Author: Shivs11