RFC for pluggable script block/AMSI logging model

[TravisEz13]

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.

[TravisEz13]

#161 (comment) was really about this issue:

Right now, I haven't done enough research to have any definitive thought about the extensibility model. Here are my current thoughts:

1. If going over the network, it must be encrypted by default.
   • Using non-encrypted traffic must have a specific Opt-In
2. I agree with @rhysjtevans, the logs should be consider an immutable source of truth..