[Android] Fix: Prevent duplicate Completed event when setting ReturnType in Entry

[bhavanesh2001]

Description of Change

This change fixes an issue where the Completed event in Entry triggers twice on Android when setting ReturnType.

Root Cause

• When setting ReturnType, Android internally updates the ImeOptions, which can cause multiple events to be fired.
• Both ImeActions (ImeAction.Done, ImeAction.Search, etc.) and physical keyboard Enter presses were not consistently handled.
• The Completed event is invoked once by the soft keyboard action (ImeAction) and again by the physical Enter key press (KeyEventActions.Up).
• This results in duplicate event triggers when pressing the return key.

Fix Implementation

• Prevent KeyEventActions.Up from firing unnecessarily if the event was already handled by the soft keyboard.

Issues Fixed

Fixes #27992

[jfversluis]

Awesome stuff @bhavanesh2001! Can we add a test for this?

[bhavanesh2001]

@jfversluis I added a test.

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[bhavanesh2001]

TappingNextMovesToNextElement is failing due to the change.

I'm a bit confused about TappingDoneClosesKeyboard. I thought the default behavior shouldn't close the keyboard, but should it?

[bhavanesh2001]

It seems like the keyboard should close when ReturnType is set to Done, as mentioned in this PR.

In the case of Search, Go, or Send, the EditorAction will be invoked for KeyEventActions (even with soft keyboard). To prevent the Completed event from being triggered twice, we can set Handled to true for these cases only. This will not interfere with cases where ReturnType is set to Next or Done.

I will include a commit for this change.

@PureWeen thoughts?

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[bhavanesh2001]

[bhavanesh2001]

/rebase

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).