Docs: Remove --add-drop-table from wp db export OPTIONS; update example

[Copilot]

--add-drop-table is already the default mysqldump behavior (enabled via --opt), so documenting it as a distinct WP-CLI option is misleading. The standalone example implied it had special significance when it does nothing beyond the default.

Changes

• Removed [--add-drop-table] from the OPTIONS section — it's a plain mysqldump pass-through, not a WP-CLI-specific flag, and is already covered by [--<field>=<value>]
• Updated example to a case where the flag is actually meaningful: pairing it with --skip-opt to explicitly re-enable DROP TABLE statements after disabling mysqldump's default --opt bundle:

# Export database with `--skip-opt` and `--add-drop-table` mysqldump flags
$ wp db export --skip-opt --add-drop-table
Success: Exported to 'wordpress_dbase-db72bb5.sql'.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[Copilot]

Pull request overview

Updates the wp db export command documentation to avoid presenting --add-drop-table as a WP-CLI-specific option when it’s simply a mysqldump pass-through, and adjusts the example to show a scenario where that flag is actually meaningful.

Changes:

• Removed --add-drop-table from the documented OPTIONS list for wp db export.
• Updated the primary example to use --skip-opt --add-drop-table together (explicitly re-enabling DROP TABLE statements after disabling --opt defaults).

---

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

[Copilot]

The new example uses pass-through mysqldump boolean flags (--skip-opt, --add-drop-table) without =<value>, but the OPTIONS synopsis currently documents extra mysqldump args only as [--<field>=<value>]. Consider updating that synopsis (or adding a short note near it) to clarify that valueless flags are supported too, otherwise this example can look like it contradicts the documented option format.