ENH: support exporting to EPANET file format #104
Description
Use Case
Users can load an EPANET model into PyPES to make modifications, but there is no way to export the model again.
Solution
Create functionality to export a PyPES model to .inp. Perhaps a new class EPANETParser to complement JSONParser is a good idea.
It may be necessary to provide an original EPANET file to fill in the more complex control information at the bottom. I don't plan to support the simulation parameters saved by EPANET directly in PyPES at the moment. I.e., the user would pass both the modified PyPES model and the original EPANET file, which would be combined into a new EPANET file.
Alternatives
Changes to EPANET models should be made to the original .inp file for the time being, and the converted PyPES model should not be modified if those changes are to be used by EPANET.