update MOAB version

[gonuke]

This appears to work using the newest release of MOAB.

Note: it probably makes sense to update the HDF5 version being used, but rebuilding it for each CI will slow things down. The alternative gets us into more complicated CI space.

Fixes #16

[ahnaf-tahmid-chowdhury]

I think it is good to go. And, while talking about updating HDF5, I think we can use h5py here as we do not need the development files, I suppose.

[gonuke]

We need the development files to build MOAB

[ahnaf-tahmid-chowdhury]

I see, HDF5 is an optional dependency of MOAB, but for our project, we require HDF5 support in MOAB. Currently, MOAB utilizes system libraries for this purpose. Since I have an active PR, I'm considering adding all the system libraries directly into MOAB itself and building the wheel package? This way, we may not need to separately install HDF5 as it will be included within MOAB.

Here's a breakdown of the pros and cons:

Pros: When installing PyMOAB, all necessary dependencies will be automatically installed.
Cons: Since these dependencies will be precompiled, we won't be able to tweak them. If modifications are needed, we'll have to build them from source.

[pshriwise]

This looks good to me! Thanks @gonuke. I'm wondering about the motivation for updating the HDF5 version. To me, we're trying to test in this package that we can reliably interpret the DAGMC data via PyMOAB, not so much whether or not the information that PyMOAB provides via the MOAB interface consistent across HDF5 versions, which seems like the responsibility of testing in MOAB itself.

[pshriwise]

Going to merge this for progress' sake. We can continue the discussion about updating the HDF5 version separately if needed.