[ENHANCE] Provide checkpoint executable options

[precicely]

Description of the Enhancement

Allow simulations to create checkpoints and later start from an existing checkpoint.

Justification for the Enhancement

The original matlab kwave binding allows one to specify a checkpoint time and a checkpoint file location. Should a simulation crash, the kwave executable can automatically pickup from it's last checkpoint.

This is super helpful for simulations that can take hours/days/weeks and one ideally does not want to have to restart such simulations from zero should their system go down for whatever reason.

Impact of Changes

Will require additional flags for simulation options and an update to the commandline interface.

[precicely]

@waltsims, do i have your blessing to clean up the execution code while I'm digging around there?

For instance, I find this section a bit puzzling:
def run_simulation(self, input_filename: str, output_filename: str, options: list[str]) -> dotdict: command = [str(self.execution_options.binary_path), "-i", input_filename, "-o", output_filename] + options
Specifically, that options are passed in as an argument but they're also an instance attribute?

Also, SimulationExecutionOptions seems a bit... strange?

For instance, some attributes are properties and reference dunders with getters/setters, others aren't. Some attributes (e.g. device_num) reference a dunder that is not made at instantiation.

[waltsims]

@precicely yes, feel free to clean up the execution code logic while adding the checkpointing feature.

[waltsims]

Tracked by #611 (Improve checkpointing parameter validation), which addresses the validation slice. Will close when that PR merges (full checkpoint executable options may need a follow-up issue if not fully covered).