Feature/log to multiple destinations

[KnifMelti]

Proposed Changes

WinGet-Install now handles all relevant mods:
$ModsPreInstall, $ModsOverride, $ModsCustom, $ModsInstall, $ModsInstalled
$ModsPreUninstall, $ModsUninstall, $ModsUninstalled

Now possible to skip install/update/uninstall from $ModsPreInstall/$ModsPreUnInstall if it has: return $false (check if App is running, etc...)

Log system extended:
1: Standard log file as it is +
2: Configuration Manager log file (if CMTrace.exe or CMLogViewer.exe exists) +
3: Windows Event Log

Related Issues

Fixes #810, Fixes #925

[KnifMelti]

@Romanitho
Megalinter: Warning PSUseBOMForUnicodeEncodedFile Write-ToLog.ps1 Missing BOM encoding for non-ASCII encoded file 'Write-ToLog.ps1'

Im using $Log | Out-File -FilePath $StandardLogFile -Append -Encoding Unicode
If I don't do that the Standard log file is kind of "garbled" from the WinGet output:

[Romanitho]

I think this is the ps1 file that is not utf8 bom

[KnifMelti]

No other ps1 file is either, but no complains for them...

[KnifMelti]

Example:

[KnifMelti]

This is a big chunk of work. I'd prefer to have each change in its own dedicated PR 😅

Yes, I know...
...but I was in a flow, and one change led to another change and all suddenly it became clear that I was rewriting nearly everything.
But it's only 10 files, and it even got a simplifying in it: 4ca0710 - (you like?)

[KnifMelti]

Something happend when I merged main into this...

[KnifMelti]

Something happend when I merged main into this...

Nah, I was wrong!
Actually it's only 6 files (the rest is mods and docu...)

[KnifMelti]

Will extract the WinGet-Install and Mods changes from this PR and create a new separate for #810