Handle insets to avoid in app message overlap on Android 15

[awardakbb]

With apps being edge-to-edge by default starting in Android 15, this PR helps avoid overlap of the message content and the system bars and cutouts when the message is opened in the InboxMode.ACTIVITY mode.

Related: #909

[awardakbb]

Hi @sumeruchat, @pdias-iterable, @davidtruong, @Ayyanchira,

Tagging you all here since you reviewed a recent PR. I was hoping to get some reviews on this one as well. We're using the Android SDK and would be great to get this fix in soon.

Thanks,
Aman

[sumeruchat]

@awardakbb Thanks we are looking into this

[Ayyanchira]

Hi @awardakbb , would you be able to provide screenshot of before and after of IterableInboxFragment handling a sample in-app getting displayed? Is the InboxFragment used on App's UI directly or is IterableInboxActivity being used?

One observation I have is: Hosting activity of the fragment may have titlebar which could obstruct the in-app content even with system bars/cutout offset. We might have to optionally check hosting Activity containing a title bar and add it to the offset.

[awardakbb]

Hi @awardakbb , would you be able to provide screenshot of before and after of IterableInboxFragment handling a sample in-app getting displayed? Is the InboxFragment used on App's UI directly or is IterableInboxActivity being used?

One observation I have is: Hosting activity of the fragment may have titlebar which could obstruct the in-app content even with system bars/cutout offset. We might have to optionally check hosting Activity containing a title bar and add it to the offset.

Hi @Ayyanchira, sure, here's before and after shots:

Our setup uses IterableInboxFragment directly to show the inbox and it uses InboxMode.ACTIVITY as the inboxMode so that it uses IterableInboxMessageActivity to open individual messages.