Comment 8 for bug 1596595

Pushed a --skip-viable Perl live test and augmented the release notes for the --skip-viable option.

For the release notes, I wanted to clarify that hold copy maps (potential copies) are updated for all processed holds in --skip-viable mode, even if the target is still viable/capturable.

This may help address a common problem where new copies are added to the database (or existing copies are modified to become holdable) but are not treated as potential copies for op-capture until the holds that use them are fully re-targeted.

In practical terms, if the targeter runs in --skip-viable mode more or less constantly, then potential copies lists will be refreshed throughout the day without unnecessarily shuffling the pull list.