Transition System Report to WP Core "Site Health Info" screen

[thomasplevy]

With the introduction of WP_Debug_Data powering the Tools -> Site Health -> Info screen we can transition from having our own system report screen and functionality and use the core methods and api.

Use WP_Debug_Data::debug_data()

Namely the filter debug_information

Remove from LifterLMS System Report (as they're now redundant)

• [ ] WordPress section
• [ ] Server section
• [ ] Theme section
• [ ] Plugins section

Add to the Core Site Health Report

• [ ] Settings (LifterLMS Settings)
• [ ] Gateways
• [ ] Integrations
• [ ] Template Overrides

Additional

• Existing "Status" screen should remain intact but the "System Report" tab should be removed (or possibly it should stay as a "tab" that directs users to the core site health screen.
• Existing data-gathering classes should remain intact as they are still utilized by our telemetry APIs for anyone opting into information tracking
• All functionality should exist behind a core WP version check (or even a `class exists( 'WP_Debug_Data' ) check. This will ensure users who haven't upgraded can still access the previous system report.

New in 5.8: https://make.wordpress.org/core/2021/06/22/extending-the-site-health-interface-in-wordpress-5-8/

[thomasplevy]

@pondermatic's question about database tables in the system report (which are present in the site-health screen) got me thinking we should prioritize this. It's not anything that anyone will really care about but it is a small improvement that will

A) Help us reduce our code footprint by getting rid of redundant code (server and wp core config stuff that already exists in site health provided by the WP core) B) By default provide us with a bunch of additional information C) I don't know if other plugins are jumping on this yet, but, if they do, it will also provide us with their data automatically if they add it (which could help us in conflict debugging)