Unify catalyst and paraview python state files
Currently, when we export a Catalyst Python state or save standard state as Python, we get two different scripts. Large parts are similar but they are different and one cannot be used in stead of the other. That makes it hard to debug and use; one can't use a Catalyst script in pvbatch for quick debugging/updating of the script or vice versa.
Here are some ideas to unify them:
- Currently, Python state has no information about extracts setup in Export Inspector. This needs to be fixed. The Python state should have full state including that of the extracts.
- Readers are typically stand-ins for simulation inputs. We need to come up with a way so that same Python snippet results in creation of reader in post-hoc mode, while creation of simulation-input-based data producer in in situ mode.