Right now we call our validate.py hook after each JS test, but not after the suite/during shutdown. Since we turned off full validation in SERVER-110331 for active nodes, we should make sure that full validation is still run before shutdown. For context, we turned off full validation in these hooks because WT::verify was racing with the oplog applier thread and causing ObjectIsBusy failures on the oplog applier thread.

We do run validate_collections_on_shutdown.js before shutting down the mongod, but since this is before shutdown, this could potentially still race with the oplog applier in the same way (but rarely as the original BFs BF-39806 and BF-38639 were produced by Antithesis runs). If this shutdown hook can still cause the race, we should consider creating a new python hook which restarts the node in standalone mode and runs full validation after each resmoke suite concludes. This would ensure that we don't hit the same race condition with the oplog applier, but still have full validation test coverage.