Maui Migrating

[AZenhom]

Steps made to make this migration happen from Xamarin to .Net Maui (.Net 7)

1. Changing inside projects namespaces to Maui instead of Xamarin
2. Creating a new solution called LocalyticsMaui, and then creating inside it new projects with the same name as the old ones, but with different project type - .Net-7 tto be specific - so for example if a project was of type Xamarin-monoandroid33, the new corresponding project is of type .net7-android33
3. copying files from old projects to their corresponding new projects but with taking that the new projects have a different architecture than the old ones
4. When trying to build the solution, all the Xamarin.Forms usage instances would now give unresolved reference errors, we have then to find the suitable alternative Microsoft.Maui components
5. The binding android and iOS projects needed some extra steps (missing .csproject configs in the new .net SDK stype project types) to make them successfully bind with the native SDKs
6. When migrating the Android & iOS sample projects (Single platform Projects), there was tons of problems, and even when they got all resolved we cannot say for sure that we guarantee the SDK working with the new Maui multi-platform project types ----> so the Android & iOS samples was replaced with a one new multi-platform Maui project, and copied all the needed files from the old ones to the new ones, with considering making now shared files instead if duplicating them for both projects, and of course there was tons of new things different from the old single-project type to take care of
7. Platform-Specific-dependency-injection won't work at all with Maui, so we had to make single interfaces implementations but with platform-specific if condition blocks inside those single implementation files
8. A vast test was performed to insure that the various Localytics features will work with no problems