Is your feature request related to a problem?

We use Bytebase to manage change review for self-hosted MongoDB. Bytebase already supports MongoDB for the SQL Editor and change workflow, but SQL Review has no rules for MongoDB: none of the rules in https://docs.bytebase.com/sql-review/review-rules list MongoDB as a supported engine, and backend/plugin/advisor has no mongodb package.

As a result, a dangerous statement such as db.orders.deleteMany({}) or db.users.updateMany({}, {$set: {...}}) passes review the same way as a targeted one. Human approval is the only safeguard.

Describe the solution you'd like

MongoDB support in SQL Review, starting with DML rules that have a direct SQL equivalent:

1. Require filter (like statement.where.require): flag updateMany / deleteMany / updateOne / deleteOne / replaceOne / findOneAndUpdate / findOneAndDelete with an empty or missing filter.
2. Limit affected documents (like statement.affected-row-limit): estimate with countDocuments(filter) or explain, and alert above a configurable threshold.
3. Disallow dangerous commands: e.g. drop, dropDatabase, remove({}), configurable allow/deny list.

The existing MongoDB parser in backend/plugin/parser/mongodb (statement splitting, query type) looks like a possible base for this.

Additional context

Is MongoDB SQL Review on the roadmap? If it is not planned, would you accept a community PR adding a mongodb advisor along these lines? Any guidance on the preferred design would help.