Create detector for Azure refresh tokens

[rgmz]

Description:

(This should only be merged after #2985.)

Azure refresh tokens are long-lived opaque tokens returned alongside access tokens¹. They can remain valid for an indefinite period, and can be used to generate a new valid access token on behalf of the subject.

This detector can be tested by obtaining a live refresh token. I like using ROADtools:

# Obtain a token for Microsoft Office
# https://learn.microsoft.com/en-us/troubleshoot/azure/entra/entra-id/governance/verify-first-party-apps-sign-in
$ roadrecon auth --device-code -c d3590ed6-52b3-4102-aeff-aad2292ab01c -r msgraph
To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code ABCDEFG123 to authenticate. 
Tokens were written to .roadtools_auth

This detector only works with refresh tokens created for public clients. If a client is confidential, the required tenant, id, and secret should trigger the service principal detector.

Checklist:

• Dependent PR merged? Add UUIDs to false positive checker #2976
• Tests passing (make test-community)?
• Lint passing (make lint this requires golangci-lint)?

Footnotes

1. https://learn.microsoft.com/en-us/azure/energy-data-services/how-to-generate-auth-token#get-an-auth-token-and-a-refresh-token ↩

[rgmz]

@ahrav In this case the token can be quite long (1000+) and the other fields can be either before or after it. What's the correct way to look +/- ~1024 on either side?

[ankushgoel27]

the refresh token doesnt always start with 0.A. it could be 1.A