Add support for Global inference profile in `AmazonBedrockGenerator`

[sjrl]

When trying to use a global inference profile in the Generator (not ChatGenerator) Bedrock component we get an error

Error: Could not auto-detect model family of global.anthropic.claude-sonnet-4-5-20250929-v1:0. model_familyparameter must be one of ('amazon.titan-text', 'ai21.j2', 'cohere.command', 'cohere.command-r', 'anthropic.claude', 'meta.llama', 'mistral'). We highly recommend using theAmazonBedrockChatGenerator instead. It has additional support for Amazon's Nova Canvas, Nova Lite, Nova Pro, DeepSeek's DeepSeek-R1, and more models.

This is due to the regex matching we do here

haystack-core-integrations/integrations/amazon_bedrock/src/haystack_integrations/components/generators/amazon_bedrock/generator.py

Lines 65 to 73 in c9ef137

	SUPPORTED_MODEL_PATTERNS: ClassVar[dict[str, type[BedrockModelAdapter]]] = {
	r"([a-z]{2}\.)?amazon.titan-text.*": AmazonTitanAdapter,
	r"([a-z]{2}\.)?ai21.j2.*": AI21LabsJurassic2Adapter,
	r"([a-z]{2}\.)?cohere.command-[^r].*": CohereCommandAdapter,
	r"([a-z]{2}\.)?cohere.command-r.*": CohereCommandRAdapter,
	r"([a-z]{2}\.)?anthropic.claude.*": AnthropicClaudeAdapter,
	r"([a-z]{2}\.)?meta.llama.*": MetaLlamaAdapter,
	r"([a-z]{2}\.)?mistral.*": MistralAdapter,
	}

Seems the issue is we only allow for 2 characters to appear before the anthropic.claude name which was fine until they added the global inference profile vs just eu or us

We should update the regex patterns to also allow it to match global

[SaraCalla]

Hi @sjrl! I would like to contribute to this issue but before doing that I would like to ask you some clarifications before start doing that.

The current pattern ([a-z]{2}\.)? is used for all 7 model families in SUPPORTED_MODEL_PATTERNS. It matches exactly 2 lowercase letters, which works for us., eu., au., ca., and jp., but fails for:
- global. (6 characters) - the case you reported
- apac. (4 characters)
- us-gov. (6 characters)
All three are valid AWS Bedrock prefixes according to their documentation.

I wanted to get your input on the scope here. Since the issue specifically mentions global, I can see a few different approaches (all would require updating the 7 patterns since they share the same prefix regex):

1. Just add global support: r"(global\.|[a-z]{2}\.)?(anthropic\.claude.*)"
   Minimal change, directly addresses the reported issue. Leaves apac and us-gov broken.

2. Fix all currently broken prefixes: r"(global\.|apac\.|us-gov\.|[a-z]{2}\.)?(anthropic\.claude.*)"
   Fixes everything that's currently broken while staying strict.

3. Explicit allowlist of all valid AWS prefixes: r"((?:global|us-gov|us|eu|apac|au|ca|jp)\.)?(anthropic\.claude.*)"
   Most comprehensive - supports all 8 current AWS Bedrock prefixes and is self-documenting.

Let me know what you think!

[sjrl]

@SaraCalla thanks for the in-depth response! I would say your option 3 sounds like the best way forward. Thanks for the help!