Does Rider provide a way to receive expiration warnings for Azure DevOps PATs while using least‑privilege scopes?

Goal: Ensure that Rider alerts users before an Azure DevOps personal access token (PAT) expires when the token is configured with the minimum scopes required for Git, NuGet, or build operations, thereby preventing unexpected authentication failures while maintaining least‑privilege principles.

Constraints: Rider stores PATs in its encrypted settings store and reuses them without attempting to refresh them; the credential UI does not show expiration dates or provide proactive warnings, and after expiration Rider only prompts for a new token following a failed Git or package operation.

Uncertainty: It is unclear whether Rider can be extended—through built‑in settings, plugins, or external integration—to surface token expiry information or to issue a warning before the token becomes invalid, especially when the token is limited to the necessary scopes.

Questions: Can Rider be configured to display the expiration date of stored Azure DevOps PATs in the credentials UI? Does Rider support a configurable pre‑expiration warning threshold for PATs? Is there a way to trigger a notification when a PAT is within a specified number of days of expiry while still adhering to least‑privilege scopes?