Updating CPP and CS winui instancing samples.

[dhoehna]

Description

The winui samples were out of date and the instancing samples demonstrated more features than just instancing making the sample confusing to follow.

I made this change because I recently was on the WinUI show and promised samples.

Target Release

1.0

Checklist

My computer can't run ARM64.

• [ X] Samples build and run using the Visual Studio versions listed in the Windows development docs.
• [X ] Samples build and run on all supported platforms (x64, x86, ARM64) and configurations (Debug, Release).
• [X ] Samples set the minimum supported OS version to Windows 10 version 1809.
• [ X] Samples build clean with no warnings or errors.
• [For new samples]: Samples have completed the sample guidelines checklist and follow standardization/naming guidelines.
• If I am onboarding a new feature, then I must have correctly setup a new CI pipeline for my feature with the correct triggers and path filters laid out in the "Onboarding Samples CI Pipeline for new feature" section in samples-guidelines.md.
• I have commented on my PR /azp run SamplesCI-<FeatureName> to have the CI build run on my branch for each of my FeatureName my PR is modifying. This must be done on the latest commit on the PR before merging to ensure the build is up to date and accurate. Warning: the PR will not block automatically if this is not run due to '/azp run' limitation on triggering more than 10 pipelines.

[dhoehna]

/azp run SamplesCI-Applifecycle

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).