Fix tool schema normalization to always remove nested function field

[Copilot]

The normalization logic had early returns that allowed tools with both top-level name and nested function fields to pass through unchanged, sending malformed schemas to Codex.

Changes

• Removed premature early returns in normalizeCodexToolChoice and normalizeCodexTools that skipped normalization when top-level name existed
• Always delete function field when present, regardless of top-level field state
• Prefer non-empty top-level name over nested function.name, with proper empty string handling

Example

Before, this tool would pass through with the function field intact:

{
  type: "function",
  name: "legacy_tool",  // Top-level name exists
  function: {           // This would NOT be removed
    name: "nested_name"
  }
}

After normalization, the function field is always removed:

{
  type: "function",
  name: "legacy_tool"  // Keeps top-level name, function field removed
}

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• dl.deno.land
  • Triggering command: /usr/bin/curl curl -s REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)