Certain components of WinUtil should be its Own Thing in a Separate Repo

[og-mrk]

Is your feature request related to a problem? Please describe.

Some parts of WinUtil can (or is) isolated from the rest of the project's code base, which can be used by other projects (outside of WinUtil), and these isolated code pieces are better managed in a separate Repo or Repos.

Describe the solution you'd like

By putting these code pieces in a separate repo, its development will be much faster, and more independent (I mean, it's basically a new project which's used by other projects, like WinUtil). This can be further managed (If Chris wants to) by putting these Repos under a GitHub Organization, allowing Chris to still be in charge of its direction and/or management, and make sure these projects are growing as expected.

Examples?

Some major parts can be isolated with some code changes here & there, like MicroWin, but we should first test this on smaller code bases (that's, if this idea ever gets approved by Chris).

Another example which can turn into it's own thing are the tools script, which are isolated scripts that can be used in any PowerShell project (at least, this's how I envision it at first), like the preprocessor (Code Formatter), and automatic dev docs by @MyDrift-user.