### What happened?

Calling `bedrock/zai.glm-5` through a litellm proxy (self-hosted) fails on multi-turn tool-calling conversations with a `BedrockException` — the `toolUseId` / `toolResult.toolUseId` values litellm sends to the Bedrock Converse API exceed AWS's hard 64-character limit.

``` litellm.BadRequestError: BedrockException - {"message":"4 validation errors detected: Value at 'messages.4.member.content.2.member.toolUse.toolUseId' failed to satisfy constraint: Member must have length less than or equal to 64; Value at 'messages.4.member.content.3.member.toolUse.toolUseId' failed to satisfy constraint: Member must have length less than or equal to 64; Value at 'messages.5.member.content.1.member.toolResult.toolUseId' failed to satisfy constraint: Member must have length less than or equal to 64; Value at 'messages.5.member.content.2.member.toolResult.toolUseId' failed to satisfy constraint: Member must have length less than or equal to 64"}. Received Model Group=bedrock/zai.glm-5 Available Model Group Fallbacks=None ```

### Root cause (best guess)

`bedrock/zai.glm-5` has no native model-registry / transform entry in litellm yet (tracked separately in #24993 and #24227). M…