[codex] Remove redundant SQLite dynamic tool storage

[sayan-oai]

Why

Dynamic tools are defined at thread start and already stored in rollout SessionMeta, which restores resumed and forked sessions. Persisting the same tools through SQLite creates a second runtime persistence path that is unnecessary prework for the explicit namespace refactor.

What changed

• Restore missing thread-start dynamic tools directly from rollout history, including when SQLite is enabled.
• Remove SQLite dynamic-tool reads, writes, backfill, and thread metadata patch plumbing.
• Add SQLite-enabled resume integration coverage that verifies a rollout-defined dynamic tool is still sent after resume.

Compatibility

The existing thread_dynamic_tools table is intentionally not dropped even though it's now unused. Older Codex binaries are allowed to open databases migrated by newer binaries and still reference this table; dropping it would break that mixed-version path. See here.

Verification

• just test -p codex-state -p codex-rollout -p codex-thread-store
• just test -p codex-core --test all resume_restores_dynamic_tools_from_rollout_with_sqlite_enabled

[sayan-oai]

@codex review this

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3dd599cb93

ℹ️ 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".