Make Connect OIDC provider registration standard for all AWS deployments

Current State

Currently, Connect OIDC provider registration for AWS integration requires custom configuration per deployment. PR rstudio/ptd#2358 demonstrates this integration by adding Connect as an Identity Provider (IdP) with hard-coded configuration specifically for an internal test workload.

Proposed Enhancement

Make Connect OIDC provider registration a standard part of every Connect deployment in AWS, enabling AWS integration to work out-of-the-box without requiring deployment-specific configuration.

Benefits

• Simplified Setup: Eliminates the need for manual OIDC provider configuration per deployment
• Consistent Experience: Provides uniform AWS integration across all Connect deployments
• Reduced Maintenance: Removes deployment-specific configuration overhead
• Better User Experience: AWS integration works immediately after deployment

Context

• Related PR: rstudio/ptd#2358 - "Use Connect as IdP for service account integration"
• Current implementation uses hard-coded configuration for a specific workload
• This should become a standard feature across all deployments

Acceptance Criteria

• OIDC provider registration is automatically configured for all new Connect deployments in AWS
• Existing deployments can be upgraded to include OIDC provider registration
• Configuration is parameterized and deployment-agnostic (no hard-coded values)
• AWS integration works out-of-the-box without additional manual configuration
• Documentation is updated to reflect the new standard behavior
• Integration tests verify OIDC provider registration across different deployment scenarios

Technical Considerations

• Ensure configuration is flexible enough to work across different AWS environments
• Consider backward compatibility for existing deployments
• Implement proper error handling and validation for OIDC provider setup
• Document any prerequisites or dependencies for the OIDC integration

Start by reviewing related PR rstudio/ptd#2358 and the existing AWS deployment configuration to locate the current hard-coded OIDC registration. Map how new and existing deployments are configured, then define tests for multiple deployment scenarios; done means parameterized registration, upgrade support, documented prerequisites, and working AWS integration without manual setup.