["1.14.2"]CallComposite ignores system insets

**Describe the bug**
When launching CallComposite, the UI ignores Android system insets (status bar and navigation bar).
The call screen is displayed fullscreen under the system bars, which makes the UI look cut off and inconsistent with other Android apps.

**To Reproduce**
Steps to reproduce the behavior:
1. Integrate CallComposite in an Android project.
2. Launch it from an AppCompatActivity.
3. Observe the call screen.
4. Notice that the UI goes under the status bar/navigation bar.
5. This bug is always reproducible.

**Expected behavior**
The CallComposite should respect WindowInsets (safe areas) and adjust UI so that it does not overlap with system bars.

**Screenshots**

**AzureCommunicationUILibrary (please complete the following information):**
- Version [1.14.2]

**Smartphone (please complete the following information):**
- Device: [Pixel 6 Emulator]
- API: [API 36]

**Call Logs**
Collect and attach call logs [Enable and access call logs](https://docs.microsoft.com/en-us/azure/communication-services/concepts/troubleshooting-info?tabs=csharp%2Candroid%2Cdotnet)

**Additional context**
In a normal Activity, this issue can be fixed by handling WindowInsets or using:

`WindowCompat.setDecorFitsSystemWindows(window, false)`

But since CallComposite manages its own Activity, developers have no direct control to fix it.

Start by reproducing the issue with CallComposite 1.14.2 on the Pixel 6 emulator using API 36, then inspect the Activity managed by CallComposite and its WindowInsets handling. The work is done when the call screen no longer overlaps the status bar or navigation bar and respects Android safe areas.

Written by the indexing model from the issue text.