fix(aionrs): handle malformed tool-call failures

[TCP404]

Summary

• Consume aionrs v0.1.30, which contains provider-side malformed tool-call sanitization and the repeated malformed tool-call loop breaker.
• Thread max_malformed_tool_call_turns through AionCore's aionrs build-extra/resolved-config path so callers can configure the breaker alongside max_turns; provider health checks set it to 1 to fail fast.
• Keep invalid empty-name tool-call stream events out of AionCore/UI emission paths, and sanitize resumed aionrs provider history by removing orphaned tool calls plus empty-name tool uses and their paired results before replay.
• Classify exhausted malformed tool-call loops as a user LLM provider problem instead of an AionUI internal error: USER_LLM_PROVIDER_INVALID_REQUEST, ownership user_llm_provider, non-retryable, resolution change_model / provider settings.

Behavior

• Aionrs still owns the actual malformed tool-call recovery loop: it writes the malformed call and synthetic error result to session history, gives the model a bounded chance to correct itself, then stops when the configured limit is exhausted.
• AionCore now passes that limit into aionrs instead of silently relying on only max_turns.
• When a weak or incompatible provider keeps returning the same malformed tool call, the UI receives a provider-owned error card rather than AIONUI_INTERNAL_ERROR.
• Strict providers no longer receive invalid replay history containing orphaned tool-use messages or empty tool names from resumed sessions.

Tests

• cargo fmt --all --check
• cargo check -p aionui-ai-agent
• cargo test -p aionui-ai-agent aionrs_build_extra_serde --lib
• cargo test -p aionui-ai-agent empty_name
• cargo test -p aionui-ai-agent history_sanitize
• cargo test -p aionui-ai-agent provider_health
• cargo test -p aionui-ai-agent classifies_provider_request_model_and_context_errors --lib
• cargo test -p aionui-ai-agent aionrs_repeated_malformed_tool_call_is_user_llm_provider_error --lib
• just push
  • migration immutability check passed
  • cargo fix --allow-dirty --allow-staged passed
  • cargo clippy --fix --workspace --allow-dirty --allow-staged -- -D warnings passed
  • cargo nextest run --workspace: 6316 passed, 18 skipped