feat(mongodb): accept string arguments in Int32/NumberInt helpers

[h3n4l]

Summary

• Allow Int32("123") and NumberInt("456") syntax in the MongoDB shell grammar, matching the existing Long/NumberLong behavior
• This aligns with real mongosh usage where users pass string arguments to numeric type constructors

Context

Bytebase uses gomongo to translate mongosh queries to native Go driver calls. Telemetry showed Int32("string") as the most frequent compatibility failure (BYT-9080). The Long/NumberLong helpers already accept string arguments — this change makes Int32/NumberInt consistent.

Changes

• MongoShellParser.g4: Changed int32Helper rule from NUMBER to (NUMBER | stringLiteral)
• Regenerated parser

Test plan

• make build && make test in mongodb/ directory passes
• gomongo integration tests pass with this grammar change

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR updates the MongoDB shell ANTLR grammar to accept string arguments for Int32(...) / NumberInt(...) helpers (e.g., Int32("123")), aligning behavior with existing Long(...) / NumberLong(...) parsing and improving mongosh compatibility.

Changes:

• Expanded the int32Helper grammar rule to accept (NUMBER | stringLiteral) instead of only NUMBER.
• Regenerated the Go parser output to reflect the grammar update.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File	Description
mongodb/MongoShellParser.g4	Updates int32Helper rule to accept string literals for Int32/NumberInt constructors.
mongodb/mongoshell_parser.go	Regenerated parser code to support the updated int32Helper alternative (NUMBER or string literal).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The grammar now accepts Int32("n") / NumberInt("n"), but the parser test suite (driven by mongodb/examples/*.js) currently only exercises numeric Int32(100) / NumberInt(100). Please add examples for the quoted-string forms (e.g., in examples/helper_functions.js) so this new syntax is covered and regressions are caught.