When attempting to write to an invalid file
location, ensure that an itk::ExceptionObject
is thrown.

When attempting to write a nifti file to an invalid location (for
example, C:\Windows\something.nii) then no file is created there yet no
error is reported.

The issue is that the error is swallowed in both niftilib and nifti2
(just "reported" with LNI_FERR macro, which does not throw an exception
or reports the error to ITK in any other way):

Resolves: InsightSoftwareConsortium#1958

Ensure that caught exceptions are converted to itk::Exception objects.

When re-using the HDF IO object, all internal
state variables should be reset to the
initial state as if the object had been
constructed anew.

Previously, the WriteImageInformation function
would set the value m_ImageInformationWritten
to true, and it would never again be set to false.

The HDF5ImageIO objects are single use for writing.  After
the initial use, the WriteImageInformation function is
short circuited, and can not be reset for writing a second image.

This bug was exposed while fixing a problem with the not
throwing an exception when attempting to write to a path
that does not exist.

This temporary work around in the test framework allows fixing
the initial problem without requiring fixing the HDF5ImageIO
re-use issues.

NOTE: Resetting the HDF5ImageIO object at the end of writing
fixes the re-use problem for non-streaming case, but that
causes the streaming tests to fail.