feat: add turn_id and truncation_policy to extension tool calls

[jif-oai]

Why

Extension-owned tools currently receive a stripped ToolCall with only call_id, tool_name, and payload.
That makes extension work that needs turn-local execution context awkward, especially web-search extension work that needs the active truncation_policy at tool invocation time.

Reconstructing that value from config or ExtensionData would be indirect and could drift from the actual turn context, so the cleaner fix is to pass the needed turn metadata directly on the extension-facing invocation type.

What changed

• added turn_id and truncation_policy to codex_tools::ToolCall
• populated those fields when core adapts ToolInvocation into an extension tool call
• added a focused adapter test that verifies extension executors receive the forwarded turn metadata
• updated the memories extension tests to construct the richer ToolCall
• added the codex-utils-output-truncation dependency to codex-tools and refreshed lockfiles

Testing

• cargo test -p codex-tools
• cargo test -p codex-memories-extension
• cargo test -p codex-core passes_turn_fields_to_extension_call
• just bazel-lock-update
• just bazel-lock-check

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cba326a3d8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".