fix(codegen): disambiguate tool names that sanitize to a JS/TS reserved word

[bug-ops]

Summary

• resolve_typescript_names now seeds the shared disambiguation used set with the JS/TS reserved word list before resolving each tool's identifier, so a tool named delete, typeof, eval, arguments, etc. gets the same numeric-suffix disambiguation as a genuine name collision instead of being emitted verbatim as an invalid function identifier.
• sanitize_ts_identifier itself is left untouched, since it is also used to sanitize object property keys, where reserved words are syntactically legal.
• Reserved-word list includes eval/arguments, which are not formally reserved words but are forbidden as a strict-mode BindingIdentifier (a function declaration's name); generated code is always an ES module, hence always strict mode.

Test plan

• test_resolve_typescript_names_disambiguates_reserved_words — unit coverage for delete, typeof, class, new, import, export, in, instanceof, void, enum, eval, arguments
• test_resolve_typescript_names_reserved_word_avoids_existing_collision — reserved-word fallback doesn't collide with an unrelated tool that already claims the fallback identifier
• test_generate_sanitizes_reserved_word_tool_name — generator-level regression test asserting the emitted .ts file never contains export async function delete( and does contain the disambiguated form
• cargo +nightly fmt --check
• cargo +stable clippy --all-targets --all-features --workspace -- -D warnings
• cargo nextest run --all-features --workspace --no-fail-fast
• cargo test --doc --all-features --workspace

Closes #133