Remove any logic using global endpoint

[tvaron3]

Summary

During a live site investigation, a failure mode was identified where SDK behavior can unintentionally concentrate data-plane traffic on the global endpoint during regional instability. The global endpoint is primarily intended for metadata operations and may lack warm address/partition caches, making it unsuitable for sustained CRUD traffic.

In scenarios where regional write targets are unavailable or excluded, repeated metadata refreshes and retries can cascade into connection failures, retry storms, and elevated CPU usage.
Rust SDK improvement opportunity: dataplane requests should never go to global endpoint. It should only be used for getting the account topology