* origin/master:
  Add poller autoscaling namespace capability (#723)
  Add request header annotation and resource-id fields (#728)
  Trampolining: addition of fields to remove the infinite loops for pinned wfs  (#721)
  Add WorkerListInfo proto for efficient worker listing (#724)
  Add storage driver info to worker heartbeats (#722)

## What changed?
Set the `PollerAutoscaling` namespace capability unconditionally to
`true`. This new capability was introduced in
temporalio/api#723.

## Why?
SDKs need to know the server supports poller scaling decisions so they
can safely scale down pollers on empty responses. Without this
capability, SDKs can't be sure the server would ever tell them to scale
back up (if the server is old).

Poller autoscaling is enabled/disabled on the worker (SDK) side — the
server always supports sending scaling decisions, so this capability is
hardcoded to `true`.

## How did you test it?
- [x] built
- [x] covered by existing tests (`TestCapabilitiesAndLimits`)

## Potential risks
None — additive capability flag, no behavioral change on the server.


Made with [Cursor](https://cursor.com)

Set the `PollerAutoscaling` namespace capability unconditionally to
`true`. This new capability was introduced in
temporalio/api#723.

SDKs need to know the server supports poller scaling decisions so they
can safely scale down pollers on empty responses. Without this
capability, SDKs can't be sure the server would ever tell them to scale
back up (if the server is old).

Poller autoscaling is enabled/disabled on the worker (SDK) side — the
server always supports sending scaling decisions, so this capability is
hardcoded to `true`.

- [x] built
- [x] covered by existing tests (`TestCapabilitiesAndLimits`)

None — additive capability flag, no behavioral change on the server.

Made with [Cursor](https://cursor.com)

## What changed?
Set the `PollerAutoscaling` namespace capability unconditionally to
`true`. This new capability was introduced in
temporalio/api#723.

## Why?
SDKs need to know the server supports poller scaling decisions so they
can safely scale down pollers on empty responses. Without this
capability, SDKs can't be sure the server would ever tell them to scale
back up (if the server is old).

Poller autoscaling is enabled/disabled on the worker (SDK) side — the
server always supports sending scaling decisions, so this capability is
hardcoded to `true`.

## How did you test it?
- [x] built
- [x] covered by existing tests (`TestCapabilitiesAndLimits`)

## Potential risks
None — additive capability flag, no behavioral change on the server.


Made with [Cursor](https://cursor.com)