Forward compatibility with upcoming Promise v3

[clue]

Builds on top of reactphp/promise#213, reactphp/promise#138, reactphp/promise#224, reactphp/socket#214 and reactphp/promise-stream#20, reactphp/promise-timer#54 and clue/reactphp-block#61
Refs clue/reactphp-http-proxy#44

[clue]

I've updated this to show that this is currently only blocked by reactphp/promise#229. The gist is that we resolve a number of promises in the same tick and its internal queue mechanism would use a different execution order for Promise v3 only. This is now addressed upstream for Promise v3 as this is the only version that shows this problem.

As an alternative, I've also looked into addressing this in this component instead, but I believe the logic to be fine and the previous Promise v3 behavior to be counter-intuitive. The code in question looks good to me and suggests outstanding promises should be rejected before the final close event is emitted:

mysql/src/Io/Connection.php

Lines 163 to 181 in 7b4428d

	// reject all pending commands if connection is closed
	while (!$this->executor->isIdle()) {
	$command = $this->executor->dequeue();
	assert($command instanceof CommandInterface);
	if ($remoteClosed) {
	$command->emit('error', [new \RuntimeException(
	'Connection closed by peer (ECONNRESET)',
	\defined('SOCKET_ECONNRESET') ? \SOCKET_ECONNRESET : 104
	)]);
	} else {
	$command->emit('error', [new \RuntimeException(
	'Connection closing (ECONNABORTED)',
	\defined('SOCKET_ECONNABORTED') ? \SOCKET_ECONNABORTED : 103
	)]);
	}
	}
	$this->emit('close');

As such, I believe addressing this in reactphp/promise#229 is the best way moving forward. The resulting patch looks surprisingly straight-forward, but together with the referenced tickets you're looking at several days worth of work on investigating this root cause and coming up with this minimal solution. Enjoy!

[clue]

Updated now that reactphp/promise#229 has been merged, this now only depends on reactphp/socket#214.

The first commit updates this to the currently unreleased Socket component to show how this only depends on reactphp/socket#214 (the build should be green). The second commit updates this to the releases that have yet to be tagged. This is expected to fail at the moment and should be green once the releases are tagged and the build is restarted.

[clue]

Restarted build now that Socket v1.12.0 has been released, this is now ready for review