Refactor telemetry and add configuration events

[florelis]

Summary of the pull request

This PR does some refactoring of the telemetry code, hopefully improving it, and adds events for configuration.

References and relevant issues

https://task.ms/44339984
Related to #117, but in a totally different direction than it suggested

Detailed description of the pull request / Additional comments

Changes to telemetry:

• Changed the name of the telemetry related classes from Logger to Telemetry. (I didn't ask if I should, so feel free to ask to rename or revert)
• Changed a couple of uses of the telemetry logger to use the file logger. We won't see these in ETW anymore, but we'll now get them with all the other logs.
• Added a file logger for the whole app that is used during initialization, and in settings. Dashboard and SetupTool still have their own log files.
• Changed the telemetry logger to only take events deriving from EventBase. This ensures that we always add privacy tags to our events and so they don't get filtered out. Also added a function to replace sensitive strings from an event's data so we always remember to remove PII
• Added telemetry events for the results of applying configuration files

Validation steps performed

Manually verified telemetry events produced with TRTT

PR checklist

• Closes #xxx
• Tests added/passed
• Documentation updated

[florelis]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[florelis]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[EricJohnson327]

/azp run

[azure-pipelines]

Pull request contains merge conflicts.

[florelis]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).