Prepare for `waveorder==1.0.0` release

[talonchandler]

I am grouping our remaining tasks to prepare for 1.0.0 into this PR. Please feel free to edit or suggest additional tasks.

• [x] remove WaveorderReader, WaveorderWriter and associated tests from waveorder
• [x] identify example scripts that we need to maintain - @mattersoflight can you help with this?
• [x] remove unmaintained examples, and ~transition the maintained example scripts to iohub~ and test
• [x] merge this PR
• [ ] release waveorder 1.0.0

This PR needs to merge before alg-dev merges.

[mattersoflight]

identify example scripts that we need to maintain - @mattersoflight can you help with this?

Here are the scripts we don't need to maintain in this repo:

• multiProcessing can be moved to recOrder.
• Reader_Writer_Examples can be deleted (since we now use iohub 🎉 ).

Here are the scripts/docs we should maintain:

• We should maintain all the other forward simulation and reconstruction example as Python scripts. We cannot maintain corresponding jupyter notebooks. They can be replaced with time-stamped PDFs within docs that are updated with every release.
• The maintained examples can be refactored as the code path evolves. These examples should also be extended with any scripts you use on regular basis.

I'll generate a few PDFs, so you can see where they fit well. I suggest we update them with every release.

Transition the maintained example scripts to iohub and test

Are you thinking of running these examples via pytest? That's an interesting idea and will allow us to test refactors. We should discuss offline which of the tests should be run during CI and which should be run manually before release.

[mattersoflight]

@edyoshikun can you help with moving the multiProcessing scripts to recOrder?

[edyoshikun]

I think we should only have 1 example for the multiprocessing on the recOrder side since the codebase is the same. The current example from @talonchandler here is a great example and the slurm scripts can serve as compliment slurm scripts PR. Also from the testing and future development and refactoring perspective, we agree it is easier to mantain.

[talonchandler]

This PR is ready for review. After discussing with @mattersoflight and looking closely at all of the examples, I partitioned the examples into two sets:

1. Maintained example scripts that "just work". I have updated scripts that demonstrate QLIPP, 3D phase, and PTI simulations and reconstructions, and I've added them to CI/CD so that we will know when they're failing. I am planning to maintain these scripts as we move through the refactor. All of these are .py files.
2. experimental_reconstructions notebooks that are dependent on specific datasets, take a longer time to run, and include a lot of duplicated code. I am planning to keep these as a form of documentation, but I am not planning to add these to CI/CD or maintain them through the upcoming refactoring.

@edyoshikun I agree that the multiprocessing example in recOrder is a cleaner version of the work here, so I removed these examples.

I'm very open to suggestions. Does the folder structure makes sense (I'm hoping the new examples/README.md helps)? I haven't added any timestamped PDFs as you suggested, but I think that the notebooks in experimental_reconstructions serve the same purpose?

[talonchandler]

@ziw-liu would you mind taking a quick look at this as well? (Also I accidentally "dismissed" the earlier review by fixing a small problem.)

@ziw-liu when this merges it will be ready for waveorder==1.0.0 release.