Implement Android to Android dynamic MTU negotiation with 250ms timeout

[krishnakumar4a4]

What to do

• Attempt request MTU from Android Wallet with 512
• If we don't receive callback in 250ms, attempt same with 185 and 100.
• If we don't receive callback from 100 as well, then we should show error to user with proper disconnection.

[Alka1703]

The following PRs implement dynamic mtu negotiation for android to android communication with a timeout of 250 ms for each negotiation. We will see an error pop up if it fails to negotiate even after 3 attempts.
PR for mosip/tuvali: mosip/tuvali#26
PR for mosip/inji:#584

The PRs have been merged in 24-02-2023 Release and the latest commit id on mosip/inji/develop is cb47493

[Alka1703]

The following PRs implements incrementing the delay time between android to android mtu negotiation to 500 ms.
PR for mosip/tuvali: mosip/tuvali#28
PR for mosip/inji: #595, #597

The PRs have been merged in 28-02-2023 Release and the latest commit id on mosip/inji/develop is 7cdee82

[krishnakumar4a4]

More context about bumping up negotiation timeout to 500ms for each MTU size

We have observed in most of the scenarios, MTU negotiation is happening quite quickly. Whereas in some device combinations, the MTUChanged callback is returning consistently after 250ms. Hence, having 250ms will only exclude those devices from leveraging the dynamic MTU negotiation implementation as all three MTU negotiation attempts with various sizes will fail. So the call was made to bump up the wait time to 500ms.

Bumping up wait time does't mean the transfer will be waiting for 500ms even if the callback is received sooner than 500ms. The wait time will be a function of min(callbackWaitTime, 500ms). Hence, having the value bumped to 500ms should not affect the device combinations that were able to negotiate quickly.