Allow runtime initialization even when only addon checks are requested

[felixarntz]

This should fix the 3rd problem outlined in #597 (comment). Also see explanation of the approach.

Note that this will only make sense to be tested in combination with #608.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: felixarntz <[email protected]>
Co-authored-by: swissspidy <[email protected]>
Co-authored-by: ernilambar <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[felixarntz]

@swissspidy Once #608 is merged, let's give this one a try. At the very least, it should fix part of the remaining problem with addon runtime checks.

[swissspidy]

Could you give it a try to implement a Behat test that runs two runtime checks, one from the addon and one built-in one?

Doesn't work. When I use e.g. --checks=non_blocking_scripts,example_runtime I still get Error: Check with the slug "example_runtime" does not exist..

[felixarntz]

@swissspidy You approved this, but I wonder whether we should keep it open until we figured out what else is missing. Just want to make sure we're not introducing something here that's wrong. WDYT?

Maybe we should reactivate those failing Behat tests in this PR and work towards making them pass.

[swissspidy]

Whether we do smaller PRs or try to fix everything in this PR, either works for me

[felixarntz]

That's fair. I guess this fixes at least part of the problem, so we could already merge it.