feat: Run setup checks by category or class

[joshtrichards]

Summary

This PR adds the ability to run:

• a specific category of setup checks
• an individual check

Implementation:

• Existing setup check category names are used for running checks in a specific category (e.g. network)
• Existing class names are used for running individual checks
• All checks still run otherwise by default so not a breaking change in behavior

Examples:

Run all checks in a specific category - e.g. the network related tests:

./occ setupchecks network

RESULT:

www-data@83e3407f887c:~/html$ ./occ setupchecks network
	network:
		✓ WebDAV endpoint: Your web server is properly set up to allow file synchronization over WebDAV.
		✓ Data directory protected
		✓ Internet connectivity
		✓ JavaScript source map support
		✓ JavaScript modules support
		✓ OCS provider resolving
		✓ .well-known URLs: Your server is correctly configured to serve `.well-known` URLs.
		✓ Font file loading
www-data@83e3407f887c:~/html$ 

Run a specific individual check - e.g. the InternetConnectivity test:

./occ setupcheck OCA\\Settings\\SetupChecks\\InternetConnectivity

RESULT:

www-data@83e3407f887c:~/html$ ./occ setupcheck OCA\\Settings\\SetupChecks\\InternetConnectivity
	network:
		✓ Internet connectivity
www-data@83e3407f887c:~/html$ 

If an unrecognized category / class is specified inform the user:

www-data@83e3407f887c:~/html$ ./occ setupchecks xxx    
Invalid type specified (or no results for that type)
www-data@83e3407f887c:~/html$ 

TODO

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[come-nc]

👍