Android - Add workaround for android 11 ime insets being weird

[emmauss]

What does the pull request do?

On android 11, forwards ime inset changes as InputPane State change events.

What is the current behavior?

On Android 11(api 30), insets have a bug where the first inset update after a config change(launching activity, orientation change) can either have 0 size, or double the actual size of the input pane on the first frame of the input pane animation. Because we calculate both the start and end bounds of the input pane at the start of the animation to enable text control editor to animate to input pane changes, on this android version, the predicted ime margin can either be covered by the input pane, or be double the input pane size at launch or when orientation changes.

What is the updated/expected behavior with this PR?

On Android 11, every change to the ime inset will be forwarded as a State change. Since the OS will send the correct insets after the animation ends, input pane margins will be corrected when the input pane is active.

How was the solution implemented (if it's not obvious)?

Checklist

• Added unit tests (if possible)?
• Added XML documentation to any related classes?
• Consider submitting a PR to https://github.com/AvaloniaUI/avalonia-docs with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

Fixes #16171

[avaloniaui-bot]

You can test this PR using the following package version. 11.2.999-cibuild0049718-alpha. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

[avaloniaui-bot]

You can test this PR using the following package version. 11.2.999-cibuild0049728-alpha. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]