h4h5tools

Prevents name conflict by always putting dimensions on the parent group of 'Data Fields'. Originally, dimensions were put on 'Geolocation Fields', and 'Data Fields' group has a hard link to it. When an EOS2 dimension and an EOS2 field have the same name, this way introduces an error because an HDF5 object name should be unique in one group. To fix this problem, the last changelist (r320) puts dimensions on the parent group of 'Data Fields' only if name conflict is detected. However, it still had a problem when:
  - an HDF-EOS2 dimension 'sharedname' is handled.
    - create dimension in the 'Geolocation Fields' group
    - create hard link to the dimension in the 'Geolocation Fields' group in the 'Data Fields' group
  - later, an HDF-EOS2 field 'sharedname' is handled.
    - tries to create an HDF5 dataset in 'Data Fields' group, but it fails because a dimension has been already converted.

If the HDF-EOS2 field is visited first, this way works. However, the order cannot be expected. This change will always put HDF-EOS2 dimensions on the parent of 'Geolocation Fields'; so, name conflict does not occur. Also, NetCDF4 has no problem in reading dimensions from its parent group.