[MS] Migrate various patch build and install issues

[wixbot]

We have resolved a number of bugs we would like to contribute back to open source in batches.

1. Always store the unresolved path even during double bind (20661). This can happen when building unresolved outputs then later binding them completely.
2. Make sure all patches are cached even if they apply to earlier packages (20682). If patches are authored later in the sequence, they may not be cached in time to be installed with an MSI already planned.
3. BA need the ProductCode in the BA.xml to determine which MSPs get installed separately and which get slipstreamed with MSIs in the package. (20864)
4. Correct logging that made diagnostics difficult along with a patch issue it covered up. (20815)
5. Support MSI 3.0-style patching while grabbing all changes (20661). There was a bug in our previous assumption when we created the patch build feature. This is necessary to still build an MsiPatchSequence table but still pull all changes into a patch. That table is necessary to trigger some MSI 3.0-style patching behavior.

Originally opened by heaths

[wixbot]

Also,

1. BA need the ProductCode in the BA.xml to determine which MSPs get installed separately and which get slipstreamed with MSIs in the package. (20864)

I see there is an open bug for part of this already, but could fix it as part of this issue.

Originally posted by heaths

[wixbot]

Also,

1. Correct logging that made diagnostics difficult along with a patch issue it covered up. (20815)

Originally posted by heaths

[wixbot]

Originally changed by barnson
Resolution set to merged
Status changed from Open to Resolved