Logging Refactor

[dafriend]

Description
Fix Chrome Logger per #2616
But wait! There's more...

• It greatly enhances how the logger parses and displays PHP variables.
• Prevents ChromeLogger from running in a production environment.
• The documentation page was redone to accommodate the configuration changes and describe the logging of variables, etc.

Checklist:

• [ x] Securely signed commits
• [ x] Component(s) with PHPdocs
• [ x] Unit testing, with >80% coverage
• [ x] User guide updated
• [?] Conforms to style guide

This might be a breaking change in that \Config\Logger has changed. Some new properties were added and others were effectively renamed.

However, the overall API is not changed and Logger still conforms to PSR-3.

[lonnieezell]

I was not able to complete a review of this code. All of changes to the config file need to be rolled back. We are not anywhere close to being ready for a BC breaking change, and almost all of the changes were unnecessary, but do to a preference.

Once that has been refactored out I can review the logic changes without all of the changes that the config file changes required.

[lonnieezell]

Why remove the examples from this list?

[lonnieezell]

This amount of text is more appropriate for user guide than a doc block. The list of levels was provided as a quick reference only.

[lonnieezell]

Please change the name back as this is definitely a BC break since this requires a change in every application that has been started on the framework so far.