Add revolt/event-loop dependency to core

Problem/Motivation

As part of #3394423: Adopt the Revolt event loop for async task orchestration the proposal to standardize async implementations on the revoltphp/event-loop package was met with enthusiasm. This issue includes the steps needed to add the dependency to the core composer files so that development using the library can begin.

Steps to reproduce

Proposed resolution

For a full reasoning of why the Revolt Event Loop over other options (such as a manual fiber implementation) see #3394423: Adopt the Revolt event loop for async task orchestration. The module evaluation has been copied below.

Dependency Evaluation

Maintainership of the package

The package is maintained by the Revolt organization which publicly consists of:

• Aaron Piotrowski who was responsible for the Fiber RFC
• Niklas Keller who was co-author on the Fiber RFC and co-maintains Amp with Aaron
• Saif Eddin Gmati Engineer at Bumble and previous Symfony memebr

Security policies of the package

The package lists that it supports the stable 1.x version and uses GitHub's private vulnerability reporting system.

https://github.com/revoltphp/event-loop/security

Expected release and support cycles

Current stable release (1.x) has existed since November 3rd 2022. There is no published release cycle but Revolt uses Semantic Versioning.

Code quality

Written by experienced developers. Covered by Psalm and PHPUnit.

Other dependencies it would add, if any (the full tree, not just direct dependencies), and evaluations for those dependencies as well

Revolt's only requirement is PHP 8.1 or newer.

It's intentionally built to be adopted by libraries to ensure that things that require an event loop work together.

Remaining tasks

• MR to update composer.json files
• Framework manager sign-off @larowlan in #12
• Release manager sign-off @catch in #4
• Write release-notes snippet

Issues after this one:
#3483239: Use revolt to prewarm caches during lock waits
#3425210: Ensure asynchronous tasks that run beyond the length of a request have the chance to complete before process exit
#3425212: [PP-1] Migrate BigPipe and Renderer fiber implementation to use Revolt Event Loop
#3257726: [meta] Use Fibers for concurrency in core
#3394423: Adopt the Revolt event loop for async task orchestration

Documentation Change

The following snippet can be added to Current PHP dependencies:

		<tr>
			<th>
			<h3 id="revolt-event-loop">Revolt Event Loop</h3>
			</th>
		</tr>
		<tr>
			<th>Repository</th>
			<td>https://github.com/revoltphp/event-loop</td>
		</tr>
		<tr>
			<th>Release&nbsp;cycle</th>
			<td>No fixed schedule. Follows semantic versioning. (<a href="https://github.com/revoltphp/event-loop?tab=readme-ov-file#versioning">Revolt Event Loop Versioning</a>)</td>
		</tr>
		<tr>
			<th>Security&nbsp;policies</th>
			<td><a href="https://github.com/revoltphp/event-loop/security">Revolt Event Loop Security Policy</a></td>
		</tr>
		<tr>
			<th>Security&nbsp;issue&nbsp;reporting</th>
			<td><a href="https://github.com/revoltphp/event-loop/security/advisories/new">Private vulnerability reporting form on GitHub</a></td>
		</tr>
		<tr>
			<th>Contact(s)</th>
			<td></td>
		</tr>

User interface changes

-

API changes

• Drupal now allows using primitives from the EventLoop provided by Revolt to schedule async tasks.

Data model changes

-

Release notes snippet

Drupal has adopted the Revolt Event Loop which is already used by asynchronous libraries such as Amphp. By adopting the event loop, Drupal lets go of managing its own Fiber invocations which simplifies implementations and improves interoperability with other asynchronous tasks. This allows Drupal contrib to make use of any async libraries that are compatible with the Revolt event loop.