If errors happen within the test, we don't want other tests to be affected by the change in value. To fix this, some of the memory tracking tests are wrapped with a try/finally so we update even after errors, some use the mochalite framework, and some just reset params at the end of the test and don't try to address this issue. Audit memory tracking tests and come up with a consistent approach.

Some tests also set/reset parameters to force the classic engine when they do not perform checks on stages of other engines (SBE). In such cases, we can just check if the SBE engine is enabled via checkSbeFullyEnabled(db), and skip the test if SBE is enabled, allowing us to not have to force the Classic engine and worry about restoring the parameter. This would save compute on rerunning these kinds of tests in the same configuration.