[Android, iOS] ContentPage.SafeAreaEdges = Default applies safe area like a container instead of being edge-to-edge (None)

### Description

When ContentPage.SafeAreaEdges is explicitly set to Default, the ContentPage applies container-like safe area padding. This contradicts the documented(https://learn.microsoft.com/en-us/dotnet/maui/user-interface/safe-area?view=net-maui-10.0#safeareaedges-enum) and intended behaviour, where Default on a ContentPage should resolve to None (edge-to-edge).

https://github.com/user-attachments/assets/b6caee7c-aaed-417d-b7df-8af38bbd6eb5

### Steps to Reproduce

1. Run the attached sample: [SafeareaIssue.zip](https://github.com/user-attachments/files/26561630/SafeareaIssue.zip)
2. Click the Default button and notice the changes.

### Link to public reproduction project repository

_No response_

### Version with bug

10.0.51

### Is this a regression from previous behavior?

No, this is something new

### Last version that worked well

Unknown/Other

### Affected platforms

Android, iOS

### Affected platform versions

_No response_

### Did you find any workaround?

_No response_

### Relevant log output

```shell

```

Start by running the attached SafeareaIssue.zip sample and compare the Default button behavior with the documented SafeAreaEdges enum. Trace ContentPage safe-area handling on Android and iOS. Done means explicitly setting Default produces the intended edge-to-edge behavior equivalent to None on both platforms.

Written by the indexing model from the issue text.