[pp-3] Convert hook_requirements to new classes or hook_runtime_requirements

For scope, wondering if we really need separate issues for all of these. E.g. the one for update (status) will be a simple move to an OOP hook_runtime_requirements(). Maybe we should group by all modules that only implement a single phase in their hook_requirements()?

• Only needs hook_runtime_requirements()
• Only needs hook_update_requirements()
• Only needs the hook_install_requirements() class
• Separate issues for each module that implements more than 1 phase

I can't wait to see system_requirements() refactored. That's going to help so much. I might even be inspired to raise my hand to at least start on that one. ;)

Opened 📌 [pp-3] Split up and refactor system_requirements() into OOP hooks Active to track it. Adding to summary.

Yeah that split was my real plan, glad to see some momentum here!

I think this is no longer postponed, but we should only create three children for now.

1. Convert all hook_requirements that only interact with phase update
2. Convert all hook_requirements that only interact with phase runtime
3. Convert hook_requirements that interact with both runtime and update if any.

Discuss here any that interact with install in any way. Discuss whether we convert those phases or wait on 📌 Create class to replace hook_install_requirements Active

There is literally one implementation in core that only interacts with update, we should just convert all requirements unless they interact with install.

Removing duplicate related issue