[hardening] fix bug on conservation checks recovery path

As the comment indicated, we need to dump the writes before attempting to recover and re-charge for gas. Failing to do this was tripping an assertion in `charge_gas`.

crates/sui-adapter/src/execution_engine.rs

@@ -337,6 +337,7 @@ fn execute_transaction<
                   // conservation violated. try to avoid panic by dumping all writes, charging for gas, re-checking
                   // conservation, and surfacing an aborted transaction with an invariant violation if all of that works
                   result = Err(conservation_err);
+                  temporary_store.reset(gas, &mut gas_status);
                   temporary_store.charge_gas(gas_object_id, &mut gas_status, &mut result, gas);
                   // check conservation once more more. if we still fail, it's a problem with gas
                   // charging that happens even in the "aborted" case--no other option but panic.

crates/sui-types/src/temporary_store.rs

@@ -536,7 +536,7 @@ impl<S> TemporaryStore<S> {
 
     /// Resets any mutations, deletions, and events recorded in the store, as well as any storage costs and
     /// rebates, then Re-runs gas smashing. Effects on store are now as if we were about to begin execution
-    fn reset(&mut self, gas: &[ObjectRef], gas_status: &mut SuiGasStatus<'_>) {
+    pub fn reset(&mut self, gas: &[ObjectRef], gas_status: &mut SuiGasStatus<'_>) {
         self.drop_writes();
         gas_status.reset_storage_cost_and_rebate();