New module Microsoft.Windows.Settings

[Gijsreyn]

• I have signed the Contributor License Agreement.
• This pull request is related to an issue.

---

This PR introduces the new Microsoft.Windows.Settings module. The module will become responsible for configuring a variety of Windows settings without the need for separate individual modules. This addresses the overall modularization, standardization, and introduces the DSC community guidelines.

Microsoft Reviewers: Open in CodeFlow

[Gijsreyn]

Hello @denelon and @AmelBawa-msft. As an attempt to address multiple challenges, e.g., script analyzer, modularization, and standardization, this is the main module Microsoft.Windows.Settings. I recognize this PR might be quite large, but yes, it's the output Sampler generates. I've explicitly left the azure-pipelines.yml file intact, so there's a reference to how it can be built up; as you mentioned earlier, the pipelines were being reviewed.

I intend to make the module the grandfather of all Windows Settings and slowly move the other modules that have either already been released or are open for pull requests to be added in here. That way, they follow a certain standard, and we don't constantly have to use the same functions repeatedly. Of course, not all registry settings have either 0 or 1. In that case, they will be more self-contained.

P.S. Perhaps the GuestConfiguration module that also uses Sampler already gots details how to build the Azure Pipelines.

[denelon]

Thanks! I've got some discussions planned today with @AmelBawa-msft to cover the roadmap for Microsoft.Windows.Setting - I think we may want to stick with the singular name, but I'm open to whichever is best for being idiomatically correct in terms of PowerShell.

[Gijsreyn]

Awesome Demitrius. I took the plural name because as with the others that were developed already, it could contain one or more settings. In this case, it will definitely contain more settings. There isn't really a strongly encouraged development guideline for module names (only for cmdlets, it should be singular), and I also took some reference from the Az module (e.g., Az.Accounts, `Az.Resources).

I'm always open to rename it to a singular.