Publish packaged exodus python bindings to PyPI

[rndubs]

The initial work to build wheels from the exodus python bindings was done in #392

This issue is requesting for the packaged bindings to be published to PyPI as a wheel and sdist, preferably for both exodus3 and exomerge3.

[mvlopri]

This is backlogged work. Unfortunately, I am not sure when I will get to this due to other priorities currently. Could you give me an idea of priority of this?

[rndubs]

My opinion is that this issue is a blocker for python projects that wish to use exodus/exomerge as a dependency. We can build and maintain wheels for our own internal usage, but we can't distribute projects that use exodus/exomerge as a dependency to downstream users since they would then need to first build the bindings/wheels themselves from SEACAS, and this isn't standard practice in the python packaging ecosystem.

Without a distribution available from PyPI, several projects have implemented their own Exodus I/O solutions using netcdf4. Some of those even came from other Sandia projects. It seems like it would be best for everyone if we could all use a common Python API for Exodus I/O.

See:

• https://github.com/sandialabs/sdynpy/blob/main/src/sdynpy/fem/sdynpy_exodus.py
• https://github.com/nschloe/meshio/blob/main/src/meshio/exodus/_exodus.py