refactor(runtime): move tool context owner boundary

[limityan]

Summary

• Move the core-owned ToolUseContext type, portable facts projection, runtime/service bindings, and unified Tool::call runtime hook facade into tool_context_runtime.rs.
• Keep framework.rs as the compatibility re-export + Tool trait boundary only; move the Deep Review post-call hook regression into the runtime owner tests.
• Update core runtime/adapter modules to import ToolUseContext from the owner module instead of relying on the framework re-export.
• Extend boundary checks and docs so future tool runtime work keeps runtime hook wiring, context owner state, and internal imports aligned with tool_context_runtime.rs.

Behavior boundary

• No tool names, schemas, manifest ordering, GetToolSpec behavior, collapsed unlock lifecycle, snapshot wrapper, concrete IO, or feature flags changed.
• ToolUseContext remains core-owned; workspace services, cancellation token, Deep Review hooks, dynamic MCP execution, Read/Edit/Write IO, and tool-result filesystem persistence are not moved out of core.
• Latest main was rebased after Improve goal mode guidance (#883); that change touches goal-mode/coordinator code and does not alter this HR-A tool-runtime owner plan.

Verification

• node scripts\\check-core-boundaries.mjs
• node scripts\\check-core-boundaries.mjs --self-test
• cargo test -p bitfun-core tool_context -- --nocapture
• cargo test -p bitfun-core tool_call_runtime_hook -- --nocapture
• cargo test -p bitfun-core call_records_deep_review_read_file_measurement_without_touching_result -- --nocapture
• cargo test -p bitfun-core product_tool -- --nocapture
• cargo test -p bitfun-core manifest -- --nocapture
• cargo test -p bitfun-agent-tools
• cargo check -p bitfun-core --features product-full
• cargo check --workspace
• cargo test --workspace
• git diff --check