#357 Add test that fails with current CTK

New file path should be used even if instance UID is already
in the database.
#357 Add test that fails with current CTK

New file path should be used even if instance UID is already
in the database.
STYLE: clarify that a variable is a query

Makes the code easier to read.
WIP - don't commit - some debugging code
Merge branch '357-dicom-insert-delete-reinsert' of github.com:pieper/CTK into 357-dicom-insert-delete-reinsert
If given a new or newly modified file, update the Images database row

Fixes #357 and is verified by ctkDICOMDatabaseTest5.

When the user imports a file that is already in the database, delete
the old row for that image and let it be re-imported so that the
database will always point to the most current location of the file
(or at least the most recently imported).
Merge branch '357-dicom-insert-delete-reinsert'

* 357-dicom-insert-delete-reinsert:
  If given a new or newly modified file, update the Images database row
  WIP - don't commit - some debugging code
  STYLE: clarify that a variable is a query
  #357 Add test that fails with current CTK
  #357 Add test that fails with current CTK