Session count in Admin UI does not match actual value

[rfc2119]

Describe the bug
The session_count column in the Admin UI http://admin-ui/scopes/global/workers does not match what the Kubernetes worker reports. The correct information is reported by the worker.

To Reproduce
Steps to reproduce the behavior:

1. On an existing cluster with Kubernetes workers, create various sessions through the Boundary CLI or Desktop
2. Debug Boundary Kubernetes worker/pod with a debug container, and run curl localhost:9203/health?worker_info=1. Example:

boundary-worker-7bf99c654b-6npfj:~# curl  localhost:9203/health?worker_info=1
{"worker_process_info":{"state":"active","active_session_count":16,"session_connections":{"s_58GnSt3uMB":6,"s_6igLFNxzla":7,"s_EKJ0efVYhn":52,"s_SaHSLwOr91":32,"s_UfmRKXKBDF":23,"s_eUvg0VYdpd":12,"s_gZVC9qmxbY":140,"s_jW6TVWI2jN":6,"s_k00mJKnDaP":57,"s_mLphb1git6":16,"s_ow0yZb3CfB":13,"s_uPIlKf8FSr":1,"s_utbfGksoiw":13,"s_vmZyhEK2pv":30,"s_vx9AMdaajZ":13,"s_xw5EkxO2wF":41},"upstream_connection_state":"READY"}}
boundary-worker-7bf99c654b-6npfj:~#

3. Go to Admin UI and notice the session count. You should see fewer sessions than the number of active_session_count field above

Expected behavior
The session count should match that reported by the worker

Additional context
Worker version: v0.14.5
Controller version: v0.14.3