Remove timeouts for platform method calls

[ben-xD]

We have timeouts for futures when making method calls to the platform side:

ably-flutter/lib/src/platform/src/platform.dart

Lines 32 to 38 in 165afcf

	.timeout(Timeouts.initializeTimeout, onTimeout: () {
	_initializer = null;
	throw TimeoutException(
	'Initialization timed out.',
	Timeouts.initializeTimeout,
	);
	});

and

ably-flutter/lib/src/platform/src/platform_object.dart

Lines 41 to 48 in 165afcf

	onTimeout: () {
	_handle = null;
	throw TimeoutException(
	'Acquiring handle timed out.',
	Timeouts.acquireHandleTimeout,
	);
	},
	).then((value) => (_handleValue = value)!);

This is timeout is not helpful, and in fact hurts developer experience (including users). They are not able to debug/ place use breakpoints properly, because the platform method times out. Additionally, slower devices platform method calls will naturally be slower. This has caused poor developer experience for me, and users in the past, for example: #72

• If a method channel or WidgetsBinding is not initialised early enough, you will get No implementation found for method MethodName, immediately.
• If the Dart VM is not initialized, then the entire app would not be running. This code would not be running either.
• If something catastrophic was happening, then that is the problem.

There is no reason to support having this timeout. I would call it a bug, because users cannot debug their applications properly or run this app on a slow device (in theory).

In #72 (comment), QuintinWillison asked

What do other libraries do to solve this?

The answer is that other libraries do not have timeouts at all, there is no reason to arbitrarily kill a platform method after any amount of seconds. So they don't actually face this problem.

I have discussed this a bit with @tiholic, thank you :).

┆Issue is synchronized with this Jira Bug by Unito

[jamienewcomb]

@ben-xD should this be closed?

[ben-xD]

@ben-xD should this be closed?

Yes, thanks @jamienewcomb