fix(ci): revert bedrock config to use api_key with AWS_BEARER_TOKEN_BEDROCK env var

The bedrock field rename from api_key to aws_bedrock_bearer_token changed
the env var name in CI config files but the CI workflows still set the
old AWS_BEARER_TOKEN_BEDROCK variable, causing SigV4 credential
resolution failures in library-mode bedrock integration tests. Revert
the CI config files to use the old field and env var names until the
rename PR lands on main with matching workflow updates.

Signed-off-by: E Geiger <egeiger@redhat.com>

Author: aegeiger

src/ogx/distributions/ci-tests/config.yaml

@@ -44,7 +44,7 @@ providers:
   - provider_id: bedrock
     provider_type: remote::bedrock
     config:
-      aws_bedrock_bearer_token: ${env.AWS_BEDROCK_BEARER_TOKEN:=}
+      api_key: ${env.AWS_BEARER_TOKEN_BEDROCK:=}
       region_name: ${env.AWS_DEFAULT_REGION:=us-east-2}
       aws_role_arn: ${env.AWS_ROLE_ARN:=}
       aws_web_identity_token_file: ${env.AWS_WEB_IDENTITY_TOKEN_FILE:=}

src/ogx/distributions/ci-tests/run-with-postgres-store.yaml

@@ -44,7 +44,7 @@ providers:
   - provider_id: bedrock
     provider_type: remote::bedrock
     config:
-      aws_bedrock_bearer_token: ${env.AWS_BEDROCK_BEARER_TOKEN:=}
+      api_key: ${env.AWS_BEARER_TOKEN_BEDROCK:=}
       region_name: ${env.AWS_DEFAULT_REGION:=us-east-2}
       aws_role_arn: ${env.AWS_ROLE_ARN:=}
       aws_web_identity_token_file: ${env.AWS_WEB_IDENTITY_TOKEN_FILE:=}