[wix-devs] 4033 - no action for superseded patch during uninstall

[Sean Hall]

The issue 6359 is covering part of the failing behavior of the failing
integration test CanAutomaticallyPredetermineSlipstreamPatchesAtBuildTime.
But the current behavior of that test is exposing what appears to be the
issue described in 4033 - the action for a patch target when the patch
state is detected as Superseded and the request state is
BOOTSTRAPPER_REQUEST_STATE_ABSENT is to leave it alone
(BOOTSTRAPPER_ACTION_STATE_NONE).

I can see that the engine won't ever do anything with a patch detected as
Obsolete or Superseded. Why? This is breaking the new registration behavior
(6297) because it's treating that patch as something that is installed and
therefore keeping the registration even though the bundle is being
uninstalled.