rate-limiting support

Azure Devops includes rate limits that could be complex to predict in an automated solution. According to the documentation, the endpoints provide headers in responses in the instances that the client has hit a rate limiting threshold.

Is responding to the Retry-After header as discussed as recommendations in the API on the roadmap?

The API uses msrest as an HTTP library, which doesn't appear to support it at this time. Note, much of the Azure SDK uses azure-core which provides Retry-After support.

先查看 issue 中連結的 Azure DevOps 速率限制與 Retry-After 文件，接著檢查用戶端如何使用 msrest，並比較 azure-core 中對 Retry-After 的支援。釐清預期範圍是否為用戶端層級的支援，並在實作前定義預期行為；done 應包含已達成共識的範圍，以及對所選行為的涵蓋。