add_virtual_resource was failing because the parent contentMetadata had no resources; this allows it to start with 0 resources (e.g. when the --purge flag is set for virtual-merge script in dor-utils)
argo uses v7 of the gem, so this will allow us to leverage this fix when we move the virtual merge script to argo.
Coverage remained the same at 91.272% when pulling 1124b08962f6ddff0b6e47fe01cd3e2019c52630 on 7-2-stable-fix-virtual-merge into 45466edcea4c95d2e2d5bb044aa4f325b98c120b on 7-2-stable.
Connects to #651
add_virtual_resource was failing because the parent contentMetadata had no resources; this allows it to start with 0 resources (e.g. when the --purge flag is set for virtual-merge script in dor-utils)
argo uses v7 of the gem, so this will allow us to leverage this fix when we move the virtual merge script to argo.