fix(ai): skip validation for provider-executed dynamic tools in v5

[pablof7z]

Description

Backport of #10734 to the v5.0 release branch.

Problem

Provider-executed dynamic tools (like Claude Code's built-in Bash tool) are being incorrectly validated in parseToolCall, causing them to be marked as invalid: true even though they execute successfully on the provider side.

This results in error messages being sent back to the model:

Model tried to call unavailable tool 'Bash'. No tools are available.

The model then gets confused and apologizes for tools it just successfully used.

Root Cause

The parseToolCall function validates ALL tool calls against the user's tools map, without checking if the tool has providerExecuted: true. Provider-executed tools aren't in the user's tools map because they're managed by the provider, not the application.

Solution

Add checks for toolCall.providerExecuted && toolCall.dynamic before attempting validation in two places:

1. When tools == null (line 31-33)
2. When tool is not found in tools map (line 111-113)

If both flags are true, call parseProviderExecutedDynamicToolCall to handle the tool call without validation.

Testing

Tested with ai-sdk-provider-claude-code v2.2.3. Before fix:

• Tool calls marked as invalid: true
• Error messages sent to model
• Model apologizes for successfully used tools

After fix:

• Tool calls properly recognized with providerExecuted: true
• No validation errors
• Model responds normally

Related Issues

• Fixes parseToolCall validates provider-executed tools causing invalid tool errors #10888
• Backport of fix(ai): provider metadata propagation for provider-executed tool results #10734

Checklist

• Added logic to skip validation for provider-executed dynamic tools
• Added parseProviderExecutedDynamicToolCall helper function
• Imported DynamicToolCall type
• Tested with real-world provider (ai-sdk-provider-claude-code)
• No breaking changes to existing behavior