Address installer component keypath and perform comprehensive setup test pass for RC2

[joperezr]

This issue tracks two important actions to ensure installer reliability for RC2:

1. Explicitly set KeyPath in installer components

• As highlighted by @joeloff in PR Fix ASP.NET Core module installer upgrade issues #60769, explicitly setting File@KeyPath="yes" in installer components is necessary to avoid future issues during upgrades or repairs. Relying on the default can lead to problems if the order of child elements changes. Reference: MSI Component Rules - Microsoft Docs.

2. Perform full setup test pass

• After merging the recent installer changes, conduct comprehensive setup scenario testing, including:
  • Clean install
  • Upgrade scenarios (from 8, 9, and 10)
  • Repair and uninstall tests for all above scenarios
  • Test success blocker behavior: Install 10.0.0-preview.2, then 10.0.0-preview.1. Success blockers should bypass the downgrade check at the bundle level (allowing the bundle to run), but the MSI should not get executed.

References:

• PR: Fix ASP.NET Core module installer upgrade issues #60769
• Key comments: Fix ASP.NET Core module installer upgrade issues #60769 (comment), Fix ASP.NET Core module installer upgrade issues #60769 (comment)

Milestone: Targeting 10.0-rc2.

/cc @wtgodbe

FYI: @halter73

[joperezr]

@wtgodbe I know you pushed a change to this to your Wix5 PR. Assuming that as soon as that one gets merged then we can go ahead and close this too? Or is there anything left to do after that one?

[danmoseley]

linking #62885 which is to fix this as well

[wtgodbe]

I know you pushed a change to this to your Wix5 PR. Assuming that as soon as that one gets merged then we can go ahead and close this too? Or is there anything left to do after that one?

Yes, that PR will close this issue