Issue Summary

When updating a feature by changing programs parent capabilities are unparented despited being associated with the same additional program. 

Steps to Reproduce

1. Step 1 - Create a feature link it to program A
2. Step 2 - Create a Capability and link it to program A
3. Step 3 - Add additional programs B & C to the capability
4. Step 4 - Update the primary program for the child feature to Program B

Expected Results

The capability shouldn't be unparented is the child work item is associated to the primary program or additional program on a capability.

Actual Results

Capability is unparented

Workaround

Users have to reparent the capability manually