Fix given_a_failed_writeback_when_a_fresh_handle_syncs_then_it_should_not_report_success

**After #4132 is merged.**

Each test below carries its reason in the `#[ignore]` attribute and its doc comment.

| Test | Location |
|---|---|
| `given_a_failed_writeback_when_a_fresh_handle_syncs_then_it_should_not_report_success` | `core/simulator/src/storage/tests.rs:2610` |

```
cargo test -p simulator --lib given_a_failed_writeback -- --ignored
```

Remove the `#[ignore]` once it passes.

After #4132 is merged, read the doc comment and #[ignore] reason for given_a_failed_writeback_when_a_fresh_handle_syncs_then_it_should_not_report_success in core/simulator/src/storage/tests.rs:2610. Run cargo test -p simulator --lib given_a_failed_writeback -- --ignored; done means the test passes and its #[ignore] attribute is removed.

Written by the indexing model from the issue text.