Telemetry opt-out

[JosephTLyons]

One of the beta blockers is adding the option to disable telemetry. I figure I would take this on, but had a few questions I wanted to ask others:

1. Should we just put if checks within the telemetry object or make the telemetry object optional to the client? I like the idea of the second option, as it bypasses the telemetry code higher up, which is probably cleaner and more efficient, but it comes at the cost of asking the user to restart the application when changing the setting, as setting the optional telemetry object happens during the init of the client.
2. Do we want to remove the command to check the telemetry log when a user opts out of telemetry? I think there are reasons to justify either option. Keeping it in would let the user check the telemetry log and make sure it is empty, to give the user a bit more assurance that we aren't sending anything. Some might like the idea of just getting it out of there for the sake of clarity.

I'll likely jump on this task soon, so it doesn't fall to the end of the task list and end up actually blocking beta. I plan to either:

1. Add the setting to the list of settings that don't get autocompleted when the user types in the settings file, so it isn't known that this exists, or
2. Omit adding the setting aspect of it, and only add the bypass code for now. I'd follow up with a PR to add the setting closer to the time where we went to officially add the feature.