TOOLS-4263 Convert mongorestore collection-options and metadata tests to Go

[autarch]

Adds integration/dumprestore/options_roundtrip_test.go: six DumpRestoreSuite methods, 18 cases in total, covering how mongorestore handles collection options and dump metadata.

JS -> Go mapping (all Go tests live in integration/dumprestore/options_roundtrip_test.go):

• test/legacy42/jstests/tool/dumprestore8.js -> TestCappedCollectionRoundTrip (integration/dumprestore/options_roundtrip_test.go) - capped collection options, secondary indexes, and eviction behavior survive a dump/restore round trip. The fixture is a plain collection with two secondary indexes plus a capped collection that has already evicted documents, and it is restored four ways to cover each granularity: from the dump root, from a single database directory into a new database name, with --nsInclude db.*, and from a single BSON file into a new collection name. Each case checks document counts, index names, the capped options, and, most importantly, that the restored collection still evicts, by inserting past the cap and asserting the count does not grow.
• test/qa-tests/jstests/restore/extended_json_metadata.js -> TestRestoreExtendedJSONMetadata (integration/dumprestore/options_roundtrip_test.go) - metadata written by very old versions of mongodump used legacy extended JSON types for numeric values, so the test hand-writes metadata in that shape, with {"$numberLong": ...} for the capped size and for an index's key, min, max, and bits, plus v: 1 indexes and an ns field, then asserts the capped options are restored and the index keys decode to plain values (_id -> 1, pos -> "2d") rather than to documents or strings. Modern mongodump cannot produce such a dump, so the fixture is built at runtime instead of being checked in, which also lets the now-unused testdata/dump_extended_json_options fixture go away.
• test/qa-tests/jstests/restore/no_options_restore.js -> TestNoOptionsRestore (integration/dumprestore/options_roundtrip_test.go) - a default restore preserves collection options while --noOptionsRestore discards them, exercised against a fixture of one capped collection, one collection with a validator, and one collection with no options, all holding the same documents. In the stripped cases the restored collections are compared against the options an actual no-options collection reports on the same server, rather than against a hardcoded empty document, because servers add default option fields over time.
• test/legacy42/jstests/tool/dumprestoreWithNoOptions.js -> TestNoOptionsRestore (integration/dumprestore/options_roundtrip_test.go) - --noOptionsRestore discards options at more than one granularity, covered by cases for a whole-dump restore and for a single-collection restore.
• test/qa-tests/jstests/restore/collation.js -> TestCollationRoundTrip (integration/dumprestore/options_roundtrip_test.go) - a collection's default collation survives a round trip, restoring both from the dump directory and from the BSON file directly.
• test/qa-tests/jstests/restore/restore_document_validation.js -> TestRestoreDocumentValidation (integration/dumprestore/options_roundtrip_test.go) - how restore interacts with document validation, in six cases: a validator on the target collection rejects the invalid half of the dump and mongorestore reports those as failures; --bypassDocumentValidation restores all of them; a validator carried in the dump's own metadata is recreated on restore and then rejects that same dump's invalid documents; --bypassDocumentValidation overrides even a validator restored that way; and --stopOnError and --maintainInsertionOrder each surface the validation error instead of swallowing it.
• test/qa-tests/jstests/restore/norestore_profile.js -> TestSystemProfileIsNotRestored (integration/dumprestore/options_roundtrip_test.go) - mongorestore must skip a system.profile collection present in a dump. The JS test could never actually reach that check, because mongodump skips every <db>.system.* namespace, so the dump it took contained no system.profile.bson and the assertion passed vacuously; the Go test instead builds a dump containing system.profile.bson and its metadata by hand, then asserts the user data is restored, system.profile is not created, and mongorestore reports zero failed inserts, the last of which is what distinguishes mongorestore skipping the file from mongorestore attempting the insert and the server rejecting it.

[autarch]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• TOOLS-4263 Convert mongodump oplog consistency tests to Go #1104
• TOOLS-4263 Convert mongodump query and data behavior tests to Go #1102
• TOOLS-4263 Convert mongodump flag validation tests to Go #1098
• TOOLS-4263 Convert mongorestore users and roles temp collection tests to Go #1097
• TOOLS-4263 Convert mongorestore drop, path and stdin tests to Go #1096
• TOOLS-4263 Convert mongorestore namespace mapping tests to Go #1093
• TOOLS-4263 Convert mongorestore bulk sizing tests to Go #1091
• TOOLS-4263 Convert mongorestore index round-trip tests to Go #1074
• TOOLS-4263 Convert mongorestore collection-options and metadata tests to Go #1073 👈 (View in Graphite)
• TOOLS-4263 Convert mongorestore replica-set oplog-replay tests to Go #1049
• TOOLS-4263 Convert mongorestore oplog-replay edge-case tests to Go #1060
• TOOLS-4263 Convert mongorestore invalid-input tests to Go #1046 : 1 other dependent PR (#1048 )
• TOOLS-4263 Delete JS tests fully covered by existing Go tests #1041
• TOOLS-4263 Add a Go test that we preserve indexes when restoring with a non-admin user on a per-data basis #1047
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.