LP#1306666: Be more mindful with transit status unwinding

LP#1306666: Be more mindful with transit status unwinding

When unwinding the copy status wrapper provided by transits, we need to
make sure we don't cause problems due to potentially broken legacy data.
One such incarnation is the "hanging transit", or a transit that should
have been closed but, through some series of events was not, and now
risks damaging a circulation that occured after the transit.  To that end,
we will avoid unwinding the copy status based on an open transit unless
the copy is in "In Transit" status.

Secondly, while hold transits aborted by staff are supposed to be followed up
by a scan of the item (either immediately if the item is in hand, or when
the item physically arrives), such does not always happen.  This can lead
to confusion of other staff members.  To help address this, we will leave
these hold transited items in "In Transit" status, so that they will not
appear available at their home location, and not show up on pull lists.

Note that because of this second change these items will not be available for
opportunistic hold capture when they are scanned in the intended, above-
described worflow, as would be the case before this commit.

Signed-off-by: Mike Rylander <mrylander@gmail.com>