Use win10-* for the RIDs

[mattleibow]

Description of Change

Use the win10-* for the RIDs to match what the Windows App SDK is doing,

The win-x64 RID means it could potentially run on Windows 7, which is not possible. Moving to win10 makes the app give a launch error. But not only that, we need to do this because the WASDK is using win10.

This can also be seen in the #3172 PR where it is required so we get the native files.

Additions made

• Updates the RID in the templates to win10-x64

PR Checklist

• Targets the correct branch
• Tests are passing (or failures are unrelated)
• Targets a single property for a single control (or intertwined few properties)
• Adds the property to the appropriate interface
• Avoids any changes not essential to the handler property
• Adds the mapping to the PropertyMapper in the handler
• Adds the mapping method to the Android, iOS, and Standard aspects of the handler
• Implements the actual property updates (usually in extension methods in the Platform section of Core)
• Tags ported renderer methods with [PortHandler]
• Adds an example of the property to the sample project (MainPage)
• Adds the property to the stub class
• Implements basic property tests in DeviceTests

Does this PR touch anything that might affect accessibility?

• Does this PR introduce a new control? (If yes, add an example using SemanticProperties to the SemanticsPage)
• APIs that modify focusability?
• APIs that modify any text property on a control?
• Does this PR modify view nesting or view arrangement in anyway?
• Is there the smallest possibility that your PR will change accessibility?
• I'm not sure, please help me

If any of the above checkboxes apply to your PR, then the PR will need to provide testing to demonstrate that accessibility still works.

[Eilon]

Seems legit. If it doesn't work on less than win10, no reason to pretend, right?