now that import log following export redirects to a new flow rather than
a 'result' state of the import flow, the import view need not be
concerned with display a view for this state
entity counts are updated even if a record is not imported due to error,
which could just be that data already exists, so user can see counts of
entities that already exist
Merge remote-tracking branch 'origin/develop' into develop
now that import log following export redirects to a new flow rather than
a 'result' state of the import flow, the import view need not be
concerned with display a view for this state
changed metadata label of importLog.existingInstruments to indicate that
there is no data in the existing instrument so data can be imported
fixed more error messaging for entities where violating MUST_EXIST was
saying the record violated MUST_NOT_EXIST

error message that Patient birthDate may be incorrect lists both
birthDate in LAVA and birthDate in data file