Add manifest based tzutil example resource

[joshcorr]

PR Summary

This adds a simple manifest based DSC Resource based on tzutil.exe. The executable is wrapped in a PowerShell call and the input/output are converted from/to JSON using PowerShell commands. This is not an ideal design of DSC Resources and I note this in the README.md, but it may prove to be a useful resource for someone learning how the manifest interacts with a binary application, which is why I am raising the PR.

PR Checklist

• Descriptive Title: This PR's title is a synopsis of the changes it proposes.
• Summary: This PR's summary describes the scope and intent of the change.
• Contributor's Guide: I have read the contributors guide.
• Style: This PR adheres to the style guide.

[github-actions]

Expectations

Thanks for your submission! Here's a quick note to provide you with some context for what to expect from the docs team and the process now that you've submitted a PR. Even if you've contributed to this repo before, we strongly suggest reading this information; it might have changed since you last read it.

This is a brief, high-level summary of what to expect from this process.

The team begins to review your PR if you request them to or if your PR meets these conditions:

• It's not a draft PR.
• It doesn't have a WIP prefix in the title.
• It passes validation and build steps.
• It doesn't have any merge conflicts.
• You have checked every box in the PR Checklist, indicating you have completed all required steps and marked your PR as Ready to Merge.

You can always request a review at any stage in your authoring process, the team is here to help! You don't need to submit a fully polished and finished draft; the team can help you get content ready for merge.

While reviewing your PR, the team may make suggestions, write comments, and ask questions. When all requirements are satisfied, the team marks your PR as Approved and merges it. Once your PR's merged, it's included when the site rebuilds.