Add telemetry entries for BinaryFormatter callsites

[MiYanni]

Related: #6858

The purpose of this PR is to add telemetry logging for all callsites of BinaryFormatter to monitor if they are actually called. Initial testing could only activate one spot, SerializeObject in ResourceSerializationService_Store.vb. All other callsites were not able to be activated with a combination of difference projects and usage of the Resource Editor. Therefore, we are adding telemetry and will monitor if there is any valid usage of this code.

Currently, we only use BinaryFormatter in the AppDesigner and Editors projects. These are both VB projects. There are bits and pieces of code that seems copy-pasted between the two. Here, the Utils file in each project has a TelemetryLogger class. I've added the same functions to each for logging usage of BinaryFormatter. The only difference between the two functions is the telemetry path has the appropriate project, appdesigner and editors respectively.

Unfortunately, the site to access the Telemetry Logger application is down. I'll be testing these changes once that site comes back up. But, I wanted to get feedback ASAP since this is for 16.9.

Edit: Even though the site for the app is down, I pulled the code for the logger, built it, and was able to test my changes. Here is a snippet of the log to show the changes are working as expected:

Remember, that's the only function I've been able to activate. But the telemetry events use the same function, so I don't expect issues with the other callsites.

Microsoft Reviewers: Open in CodeFlow

[MiYanni]

After the changes above, the appropriate properties are still being recorded.