RFC for pluggable script block/AMSI logging model

from #161/ #106

@PowerShell/powershell-committee discussed this one in detail today. We believe that there's massive value in figuring out how to tee ScriptBlock and AMSI style logs off to remote logging providers, but a bunch of the semantics in this RFC are specific to Splunk.

Instead, we think an RFC should be authored that builds a provider/plugin model for allowing multiple remote logging providers. This RFC should also give consideration to whether local logging targets should be treated the same way (e.g. if you want to exclusively log to a remote target, maybe in serverless/stateless scenarios). There should also be a consideration of whether we should have something like a Get-PSLog or Write-PSLog that are agnostic to logging providers.

The PowerShell Team has a strong interest in picking this up, but we have no idea when we can get to it right now. We only know that it should be a flexible, pluggable model.

首先阅读这份 RFC 以及 issues #161 和 #106，然后查看 issue 中引用的 PowerShell Committee 讨论。拟议的工作是一份关于灵活的 provider/plugin 模型的 RFC，用于 ScriptBlock 和 AMSI 风格的日志记录，涵盖多个远程 provider、本地目标，以及 Get-PSLog 或 Write-PSLog 等与 provider 无关的命令。