This is a follow-up of https://jira.mongodb.org/browse/SERVER-124431

As mentioned in BF https://jira.mongodb.org/browse/BF-41586 it is known that sometimes the generation of a mini-dump on a Win32 platform can fail. This is problematic for those tests where a crash of the server is part of the test itself.

This tickets is to investigate which other tests should be marked in the same way as those changed in https://jira.mongodb.org/browse/SERVER-124431.

An initial investigation, done using Claude, revealed the following tests, which are marked with TestData.cleanUpCoreDumpsFromExpectedCrash = true, and which are therefore candidates for this setting:

noPassthrough/
  - logging/log_backtrace.js
  - oplog/oplog_application_while_recovering_must_succeed.js
  - exit_logging.js
  - index_builds/index_build_killop_secondary_after_commit.js
  - index_builds/index_build_killop_secondary_before_commit.js
  - index_builds/index_secondary_awaiting_primary_abort_crash_on_commit.js
  - index_builds/index_secondary_commit_after_scan_error.js

  replsets/
  - oplog_replay_on_startup_with_bad_op.js
  - resync_majority_member.js
  - startup_recovery_for_restore_needs_rollback.js
  - stepdown_fassert_on_rstl_timeout.js

  sharding/
  - health_monitor/config_fault.js
  - health_monitor/config_server_health_observer_crash.js
  - replica_set_to_csrs_promotion.js

  disk/
  - log_metadata.js

  multiVersion/
  - genericBinVersion/server-catalog-and-routing/replica_set_to_csrs_promotion_startup_flag.js

  ssl/
  - x509_startup_warning.js
  - ssl_cert_selector_apple.js

  resmoke_selftest/
  - shell_hang_analyzer.js

This could also be extended further to include all the tests which havea 'allowedExitCode: MongoRunner.EXIT_ABORT'.