chore: Prevent Uno desktop CI from requiring Android workload

[w-ahmad]

Description

Updates the Uno desktop sample CI build to avoid requiring the Android workload when only the net10.0-desktop target is being built.

Although the CI job explicitly builds net10.0-desktop using -f net10.0-desktop, the implicit restore can still evaluate all frameworks listed in TargetFrameworks, including net10.0-android. On the latest GitHub-hosted Windows runner, this results in NETSDK1147 because the Android workload is not registered.

This change passes:

-p:TargetFrameworks=net10.0-desktop

to the desktop build command so the restore and build are scoped exclusively to the desktop target framework.

This keeps the desktop CI job isolated from workloads that are unrelated to the target it is responsible for building.

Related Issue

N/A

Type of Change

• 🐛 Bug fix
• ✨ New feature
• 📝 Documentation update
• ♻️ Refactor
• 🧪 Test
• 🔧 Chore / maintenance

Checklist

• This PR is not from my main branch
• Tested with WinUI target
• Tested with Uno Platform target
• Unit / integration tests added or updated
• Documentation updated to reflect changes
• Code follows the project's coding conventions

Screenshots / Recordings

N/A — CI-only change.

Additional Notes

The CI failure started after an update to the GitHub-hosted Windows runner environment. No application or library behavior is changed by this PR.

The Uno desktop CI job should only require and evaluate net10.0-desktop; Android, iOS, and WebAssembly targets are handled separately.