Erase may take more than a second about mcumgr-android

[bgiori]

1 second seems very short for a timeout. I think we should bump the timeout for all operations. Maybe something ~5s?

[philips77]

This should work for all current devices, but may also be parametrised. At least in the transport interface an additional parameter with timeout? Or not worth changing the API?

[bgiori]

I think it would be best to leave it up to the transport implementation. It could be nice to expose the timeout through the interface, but I cant think of a good use case as of now, so it may be more cluttering than what it's worth. For now I think we should:

1. Parameterize timeout in McuMgrBleTransport with getter/setter
2. Bump the timeout from 1s to 4-5s

[philips77]

True. Let's do 2. then.

[bgiori]

Fixed in ceca338