[uAMQP] Smarter refresh token window

[yunhaoling]

This is spawned from the issue: #20086

• The token returned by the AAD service maybe a cached one.
• The service would refresh the token on their side within their refresh window.
• uAMQP would refresh the token on its own refresh window.
• So if there's gap between the uAMQP refresh window (e.g. 6mins) and the service refresh window (e.g. 5 mins), then during the gap (e.g. 1min), uAMQP would keep trying to refresh the token blocking sending/receiving flow.

We should improve the behavior to have a smarter version of token refreshing strategy.

azure-core ref: https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/core/azure-core/azure/core/pipeline/policies/_authentication.py#L71

---

• allow setting refresh window
• do not put token onto the link if the new token is equal to the old one
• introduce backoff if the new token is equal to the old one
  • no throttling service
  • however, the current auth state set is a problem
    • currently it is refresh_required -> auth_in_progress
    • we need a kinda new status: refresh_required + can_work, which indicates token refresh is required but we should still keep working