Bug: When a bad state change is hit the raid doesn't produce results YAML file

[sarahecraddock]

When using the new bad state change functionality, and a bad state change occurs, I see the following trace logging and no results YAML file is written:

2025-01-31T15:27:39.988Z [INFO]  2025/01/31 15:27:39 [ERROR] Change in test 'CCC_ObjStor_C03_TR01_T04' failed to revert. Change name: delete_blob_container
2025-01-31T15:27:39.988Z [INFO]  2025/01/31 15:27:39 [ERROR] TestSet failed to revert changes, halting execution to prevent further impact
2025-01-31T15:27:39.988Z [ERROR] CCC.ObjStor.C03: One or more changes failed to revert, and the system may be in a bad state. See logs or test details for more information.
2025-01-31T15:27:39.988Z [INFO]  2025/01/31 15:27:39 [ERROR] Change in test 'CCC_ObjStor_C03_TR01_T04' failed to revert. Change name: delete_blob_container
2025-01-31T15:27:39.988Z [TRACE] Mobilization complete
2025-01-31T15:27:39.988Z [INFO]  2025/01/31 15:27:39 !Bad state alert! One or more changes failed to revert. See logs for more information