Support project-specific client credentials

[mpgxvii]

Currently, the Rest-Source-Auth uses a global client ID and secret for each data source client (e.g., Fitbit, Garmin, etc.). This setup limits flexibility when different projects require separate credentials for the same client.

Goal
Allow configuring client credentials per project, while maintaining a global default fallback. This will make it easier to support multiple projects with different OAuth configurations, improving security isolation and maintainability.

Proposed Changes

• Update configuration and data model to support specifying client_id and client_secret per project per client.
• When authenticating users: Check if project-specific credentials exist for the client. If found, use them. Otherwise, fall back to the global credentials.
• Ensure backward compatibility for existing configurations using only global credentials.

[yatharthranjan]

how does below config looks

restSourceClients:
  - sourceType: FitBit
    authorizationEndpoint: https://www.fitbit.com/oauth2/authorize
    tokenEndpoint: https://api.fitbit.com/oauth2/token
    projects:
      default:
           clientId: <CLIENT_ID>
           clientSecret: <CLIENT_SECRET>
           scope: activity heartrate sleep profile
      project_ABC:
           clientId: <CLIENT_ID>
           clientSecret: <CLIENT_SECRET>
           scope: activity heartrate sleep profile
      project_XYZ:
           clientId: <CLIENT_ID>
           clientSecret: <CLIENT_SECRET>
           scope: activity heartrate sleep profile

So it tries to find the project name, if not present, it will use the default credentials as fallback

[yatharthranjan]

What about clients of rest-source-auth (such as connectors, push endpoint), presume we would need to add project specific configs there too?