Add strings_pull and strings_push tools

[Stefan Bruhns (sbruhns)]

Summary

• Adds strings_pull tool: downloads locale files based on phrase.yml pull targets, supports <locale_name>/<locale_code> placeholders, tag filtering, and branch downloads (automatically resolves branch project ID via branchShow — the Phrase API requires the branch's own project ID for locale downloads)
• Adds strings_push tool: uploads locale files from phrase.yml push sources with glob expansion (including **), locale extraction from path patterns, tag tagging, and async upload polling
• Adds shared phrase_config.ts for config parsing, placeholder substitution, and glob-to-regex conversion
• Adds BranchesApi to StringsClient (needed for branch project ID resolution in pull)
• 16 integration tests using Polly VCR cassettes recorded against the real mcp-pull-push-test Phrase project — run in replay mode with no network or token required

Test plan

• npm test — all tests pass in replay mode
• Re-record cassettes with POLLY_MODE=record PHRASE_STRINGS_TOKEN=<token> npm test -- src/products/strings/tools/pull.test.ts then ...push.test.ts (run files separately to avoid rate limiting)
• Verify strings_pull via MCP: point at a real phrase.yml and confirm locale files are written to disk
• Verify strings_push via MCP: push locale files and confirm uploads appear in Phrase Strings

🤖 Generated with Claude Code

[Manuel Boy (docstun)]

Stefan Bruhns (@sbruhns) since you introduced replay tests with this change, I suggest adding some documentation how to re-generate those in the README.

[Sönke Behrendt (theSoenke)]

This basically emulates the CLI pull command? It probably works for really basic configs but there are a lot more options that are not supported and we'd need to fully reimplement the target parsing if it should be compatible with the config