Some writers performs their writes in the destructor

I understand why this is done, but it is likely not a great situation. I think writing should occur at the end of `Sequencer::run` and not when the sequencer is deallocated.

I propose we either:

1. Refactor `JsonMaterialWriter` (and consequently `MaterialMapping`) so that it can become an `IWriter`, that gets an `endRun` call when the event loop finishes.
2. Add functionality to `Sequencer` such that algorithms also receive an `endRun` (or `finalize`?) call, so that `MaterialMapping` can call a write function on `JsonMaterialWriter`.

What do you think @Corentin-Allaire?

Start by reading Sequencer::run, JsonMaterialWriter, and MaterialMapping, then review the seven-comment discussion and the two proposed lifecycle designs. The scope is not settled; done would require an agreed write lifecycle in which writes no longer depend on destructor deallocation and the selected design is implemented consistently.

由索引模型根據 Issue 內容生成。