Update the MAUI sample to CSLA 11 with trimming and NativeAOT #4970

Background

CSLA 11 makes the framework, including Csla.Xaml for MAUI, trim and NativeAOT compatible (#3347, #4955, #4962). Samples/MauiExample still targets CSLA 10 packages and doesn't publish with trimming or NativeAOT, so it doesn't show how to build a MAUI app on CSLA 11 that does.

This issue covers the trimming and NativeAOT part of moving the MAUI sample to CSLA 11. The general sample changes, such as the RefreshAsync updates and the #1766 view model behavior changes, are tracked in #4961.

Work

1. Move to CSLA 11 packages. BusinessLibrary references Csla and the retired Csla.Generator.AutoImplementProperties.CSharp 10.0.0 beta, and MauiExample references Csla.Maui 10.0.0 beta. Remove the generator package (it fails the build with CSLABUILD001 in CSLA 11) and reference the CSLA 11 Csla and Csla.Maui packages. This depends on a published Csla 11 package and on Add MAUI support for version 11 #4924.
2. Business classes.
   • Declare PersonList partial (CSLA0024), so the operations generator handles its data portal methods.
   • Replace Csla.Data.DataMapper.Map(data, this) in PersonEdit with explicit property assignments. DataMapper.Map is [RequiresUnreferencedCode].
3. Publish with trimming and NativeAOT.
   • Enable full trimming (TrimMode=full) for Android and iOS.
   • Enable NativeAOT where MAUI supports it (PublishAot on iOS and Mac Catalyst).
   • Set TrimmerSingleWarn=false so warnings are reported per member.
   • Set IsAotCompatible on BusinessLibrary and DataAccess, so they are analyzed at build time.
   • Remove the stale net9.0 property groups from MauiExample.csproj.
4. Get to zero IL warnings.
   • PersonEditPage.xaml uses csla:PropertyInfo, which CSLA 11 marks [RequiresUnreferencedCode] because it walks a string binding path. Decide whether the sample keeps it and documents the warning (the binding source is a business object, so it is preserved), or shows an alternative.
   • Keep compiled bindings (x:DataType) everywhere.
5. Verify. Publish a Release build for at least Android and one Apple target with NativeAOT. Then run the app and exercise list, edit, save and validation.
6. Readme. Update the sample's readme with the project settings and the CSLA-specific rules.

References

• Trimming and NativeAOT guide for CSLA 11 (csla-mcp): csla-examples/v11/TrimmingAndNativeAot.md
• "Trimming and NativeAOT annotations" in docs/Upgrading to CSLA 11.md
• Related: Add MAUI support for version 11 #4924 (MAUI support for CSLA 11), Use non-generic RefreshAsync in samples when they move to CSLA 11 #4961 (sample updates for CSLA 11), Resolve trimming and NativeAOT warnings in the other CSLA assemblies #4962 / Resolve trim and NativeAOT warnings in the other CSLA assemblies #4969 (trim and NativeAOT support in the other CSLA assemblies)