arm64 test failures due to HDF5 issue

[rfiorella]

Two of the ATS regression tests are failing because there is a difference in the type of HDF5 variables in the test files.
For example, mpi_num_procs is interpreted as a 32 bit integer on x86_64/amd64 (H5T_STD_I32LE), but a 64 bit integer on arm64 (H5T_STD_I64LE).

In my most recent test, this causes the following test failures:

	223 - ats_regression_test-08_energy-permafrost-wrm_vangenuchten-krel_vangenuchten (Failed)
	224 - ats_regression_test-08_energy-permafrost-wrm_vangenuchten-krel_brookscorey (Failed)
	225 - ats_regression_test-08_energy-permafrost-wrm_vangenuchten-krel_sutraice (Failed)
	226 - ats_regression_test-08_energy-permafrost-wrm_brookscorey-krel_brookscorey (Failed)

however, given where this variable is set, this might actually be an Amanzi or ascemio issue.

[rfiorella]

@ecoon @jd-moulton I am pretty sure this is an ascemio issue. parallelIO sets the types as HDF5_NATIVE_*, which can be interpreted differently across architectures.

I think replacing the H5T_NATIVE_* with H5T_STD_* types in ascemio should fix this, if we want to bump the version of that as well with the upcoming release (I'm happy to patch and test this if this seems like a good route forward).

Otherwise the test infrastructure will need to be made a bit more permissive to these type mismatches.

Edit: actually this might even be a bit more interesting, as I'm currently getting different behavior on M1 vs M2 chips. Need to check again to make sure that the container images and docker versions I'm using are identical.

[rfiorella]

M1 failures are:

	223 - ats_regression_test-08_energy-permafrost-wrm_vangenuchten-krel_vangenuchten (Failed)
	224 - ats_regression_test-08_energy-permafrost-wrm_vangenuchten-krel_brookscorey (Failed)
	225 - ats_regression_test-08_energy-permafrost-wrm_vangenuchten-krel_sutraice (Failed)
	226 - ats_regression_test-08_energy-permafrost-wrm_brookscorey-krel_brookscorey (Failed)

(these all seem to be HDF5 type mismatches)

M2 failures are:

	170 - executable_mesh_factory_np2 (Timeout)
	171 - executable_mesh_factory_np4 (Timeout)
	226 - ats_regression_test-06_transport-column_infiltration_subcycled_restart (Failed)
	258 - ats_regression_test-08_energy-permafrost-wrm_vangenuchten-krel_brookscorey (Failed)

the executable_mesh_factory parallel test failures appear to be an issue with mesh extraction.
haven't located the reason why the transport and energy tests failed - the logs in both cases refer to a stdout file that doesn't seem to exist.