Explicitly set AWS bedrock region in e2e tensorzero.toml (tensorzero#830

)

The default provider in the AWS `RegionProviderChain` will try many
different strategies to detect the region, including making network
requests to '169.254.169.254' (which will time out when not running
on AWS).

We should change our behavior to avoid this footgun (e.g. require
an explicit opt-in for this network-based region detection behavior).
For now, let's speed up the test server by explicitly setting the
region, which will skip the region-detection logic

tensorzero_internal/tests/e2e/tensorzero.toml

@@ -58,6 +58,7 @@ model_name = "claude-3-haiku-20240307"
 [models.claude-3-haiku-20240307.providers.aws-bedrock]
 type = "aws_bedrock"
 model_id = "anthropic.claude-3-haiku-20240307-v1:0"
+region = "us-east-1"
 
 [models.claude-3-haiku-20240307-us-east-1]
 routing = ["aws-bedrock-us-east-1"]
@@ -98,6 +99,7 @@ routing = ["aws-bedrock"]
 [models.claude-3-haiku-20240307-aws-bedrock.providers.aws-bedrock]
 type = "aws_bedrock"
 model_id = "anthropic.claude-3-haiku-20240307-v1:0"
+region = "us-east-1"
 
 [models.claude-3-haiku-20240307-gcp-vertex]
 routing = ["gcp_vertex_anthropic"]