fix!: Move SwipeControl to MUX

[Youssef1313]

BREAKING CHANGE: Move SwipeControl, SwipeItem, SwipeItemInvokedEventArgs, SwipeMode, SwipeItems, and SwipeBehaviorOnInvoked implementation from WUX namespace to MUX namespace.

GitHub Issue (If applicable): Part of #8339

PR Type

What kind of change does this PR introduce?

What is the current behavior?

What is the new behavior?

PR Checklist

Please check if your PR fulfills the following requirements:

• Docs have been added/updated which fit documentation template (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Validated PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Associated with an issue (GitHub or internal) and uses the automatic close keywords.
• Commits must be following the Conventional Commits specification.

Other information

Internal Issue (If applicable):

[jeromelaban]

I don't think we need to do that one. It's already in the proper namespace when running for WinUI, so that would be an unnecessary change for the UWP targets. What do you think @MartinZikmund ?

[MartinZikmund]

@jeromelaban I think it is still relevant for UWP as well - similarly to other controls like NavigationView, SwipeControl and others are more up-to-date and have latest fixes in WinUI 2.8, so apps targeting UWP will most likely use the MUX version it instead of the WUX version. When porting such apps, it would mean the developer would have to make a uno-specific XAML to include both MUX version on UWP and WUX version on Uno targets, which would be quite ugly. Alternative solution would be to copy the same implementation to both MUX and WUX namespace, but I assume most people will no longer use WUX version anyway, so this should be simpler.

[Youssef1313]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[jeromelaban]

Some tests are failing it seems:

[MartinZikmund]

Coolington!

[MartinZikmund]

Coolington!