Support OAuth access tokens as Reporting API credentials

[SanjayVas]

Specifically RFC 9068 Access Tokens. This is in addition to mTLS authentication, which will need to be supported for existing callers. For proxying (e.g. grpc-gateway), OAuth access tokens will be the only supported authentication credential type.

• feat: Add utilities for extracting authentication credentials from gRPC calls common-jvm#288
  • fix!: Verify audience claim matches client ID for OpenID provider common-jvm#290
  • Revert "fix!: Verify audience claim matches client ID for OpenID provider" common-jvm#294
• feat: Add libraries for Access API clients #2003
• fix: Make client auth optional when --require-client-auth is false common-jvm#300
• feat!: Allow private key to be specified to OpenIdProvider common-jvm#299
• feat!: Add overload of verifyAndDecodeBearerToken using credentials common-jvm#301
• fix: Accept (and require) JWT type header for RFC 9068 tokens common-jvm#302
• Use Access API for Reporting service authorization #2021
• feat!: Accept RFC 9068 OAuth tokens as Reporting API credentials #2063

https://rally1.rallydev.com/#/?detail=/userstory/815903454985&fdp=true