Show Task Queue Stats in describe-version and don't use SDK anymore

[carlydf]

What was changed

Show Task Queue Stats in describe-version and don't use SDK anymore

Here is how the Task Queue Stats output looks now. If priority keys are not being used, the Stats by Priority section is omitted.

 % ./temporal worker deployment -n worker-controller-demo.a2dd6 --api-key=$APIKEY --address=us-east-1.aws.api.temporal.io:7233 describe-version --deployment-name helloworld-demo/staging --build-id  v0-3-0-good-patch-5db8 --report-task-queue-stats 
Worker Deployment Version:
  DeploymentName      helloworld-demo/staging
  BuildID             v0-3-0-good-patch-5db8
  CreateTime          5 months ago
  RoutingChangedTime  5 months ago
  CurrentSinceTime    5 months ago
  RampingSinceTime    a long while ago
  RampPercentage      0
  Metadata            map[temporal.io/controller:metadata:{key:"encoding" value:"json/plain"} data:"\"temporal-worker-controller/temporal-system\"" temporal.io/controller-version:metadata:{key:"encoding" value:"json/plain"} data:"\"carly-demo\""]

Task Queues:
     Name        Type    ApproximateBacklogCount  ApproximateBacklogAge  BacklogIncreaseRate  TasksAddRate  TasksDispatchRate
  hello_world  workflow                     3659        3993h56m37.338s                    0             0                  0
  hello_world  activity                        0                     0s                    0             0                  0

Stats by Priority (hello_world / workflow):
  Priority  ApproximateBacklogCount  ApproximateBacklogAge  BacklogIncreaseRate  TasksAddRate  TasksDispatchRate
         3                     3659        3993h56m37.338s                    0             0                  0

Stats by Priority (hello_world / activity):
  Priority  ApproximateBacklogCount  ApproximateBacklogAge  BacklogIncreaseRate  TasksAddRate  TasksDispatchRate
         3                        0                     0s                    0             0                  0

Why?

Want to show task queue stats, don't want to depend on unreleased SDK changes

Checklist

1. Closes

2. How was this tested:
   New functional test and ran locally

3. Any docs updates needed?