h4h5tools

Change an HDF-EOS2 field name if it contains the slash so that netCDF-4 (HDF5) does not understand it as a delimiter.

An HDF4 SDS representing an HDF-EOS2 fiele does not have this problem because existing code has been handling correctly. This problem happened only if an HDF4 Vdata representing an HDF-EOS2 field is converted into an HDF5 dataset. For this case, converting an HDF4 Vdata is done in the HDF-EOS2 specific routine, and this routine didn't correct the name.

This changelist lets the new routine call correct_name() and so on so that the slash can be replaced by underscore.

After this change, all test cases passed. However, this should be supported by more harsh test cases.