Next steps for PromiseTimer with ReactPHP v3

Start with the ReactPHP v3 roadmap discussion, the linked PromiseStream issue, and the referenced dependency-removal pull requests. Review PromiseTimer's Packagist dependents and decide whether to move it to Friends of ReactPHP, reuse its logic elsewhere, or deprecate it; the issue is done when the project direction is agreed.

We're currently moving forward with working on ReactPHP v3 and releasing the roadmap tickets for all our components (see https://github.com/reactphp/event-loop/issues/271 and others). We still have some components that we haven't finalized plans for, especially with the next major version approaching. It's important to address how we can make sure these components are aligned with the upcoming ReactPHP v3.

This discussion about the PromiseTimer component is somewhat similar to reactphp/promise-stream#40 and https://github.com/orgs/reactphp/discussions/475. We already started to remove additional dependencies of PromiseTimer where possible (see https://github.com/reactphp/socket/pull/305, https://github.com/reactphp/dns/pull/213, clue/reactphp-redis#154 and others) and after taking a look at Packagist, it seems like PromiseTimer is only used as a dev-dependency for tests in other ReactPHP components.

This raises the same questions as in PromiseStream, should we move the ReactPHP PromiseTimer component to Friends of ReactPHP, or should we simply reuse the logic elsewhere and deprecate the component afterwards together with the EOL of ReactPHP v1.

Happy about input on this, so let's discuss possible options and decide on what makes the most sense 🚀