🪙 feat: Add Support for new AWS Bedrock API Keys

[dustinhealy]

Summary -- Work In Progress (just UI)

This PR enhances UI support for Bedrock credentials, including the new AWS Bedrock Bearer Tokens https://docs.aws.amazon.com/bedrock/latest/userguide/api-keys-use.html

Core Features

Frontend Changes: Bedrock Credentials UI

• Added form fields for AWS Access Key ID, Secret Access Key, Session Token, and Bedrock Bearer Token in SetKeyDialog and BedrockConfig components. [1] [2]
• Updated DialogManager.tsx to pass relevant userProvide flags for Bedrock credentials. [1] [2]

Backend Changes: Placeholder for Bedrock Credential Handling

• Modified environment variable checks and flags in EndpointService.js to prepare for future backend logic to handle Bedrock credentials.
• Added properties (userProvideAccessKeyId, userProvideSecretAccessKey, userProvideSessionToken, userProvideBearerToken) to the getEndpointsConfig function to facilitate credential detection.

Localization Updates

• Added new translation strings for Bedrock credentials in translation.json.

Change Type

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Translation update

Details & Change Breakdown

1. Server-Side Refactor (EndpointService.js and getEndpointsConfig.js)

• Added checks and flags for user-provided Bedrock credentials in environment variables.
• Modified getEndpointsConfig to include user-provided credentials properties for Bedrock.

2. Client-Side Refactor

• MCPPanel.tsx and SetKeyDialog.tsx: Added input fields and translations for various Bedrock credentials.
• DialogManager.tsx: Updated user-provided credential flags for Bedrock.

3. Localization Updates

• Added strings for new Bedrock credential fields in translation.json.

Testing

• Verified UI components display correct input fields for Bedrock credentials based on environment flags.
• Ensured user supplied BEDROCK_AWS_ACCESS_KEY_ID, BEDROCK_AWS_SECRET_ACCESS_KEY, and
  BEDROCK_AWS_SESSION_TOKEN allowed user to successfully send and receive queries in chat.

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have commented in any complex areas of my code
• I have made pertinent documentation changes
• My changes do not introduce new warnings
• Local unit tests pass with my changes

[dvejsada]

@dustinhealy Is this ready for review?

[danny-avila]

this one should be merged first

#10504