Implement Powershell Log parsing

[YahavArm]

implement powershell logging parsing to extract possible indicators for malicious behavior resolves #1200 #593

[YahavArm]

there are also other events which can indicate malicious activity such as 4100 and event 400 in the Windows PowerShell log

[YahavArm]

this MR was changed to draft as i need to implement tests, and currently having trouble with creating test data

[YahavArm]

Maybe it'd be nice to convert the existing powershell_history plugin to a powershell namespace plugin, move powershell_history to powershell.history and move this code to powershell.scriptblocks?

We do a similar thing with defender.evtx.

This is essentially a project-wise style choice, of which i am not aware how much complexity it will add to this plugin and to powershell history

[Schamper]

This is essentially a project-wise style choice, of which i am not aware how much complexity it will add to this plugin and to powershell history

Not much complexity I think, just better to consolidate that. This plugin isn't that much code either so it fits well together.

[YahavArm]

i combined the powershell plugins into the powershell namespace plugin and rewrote the event iteration the prevent the entire event log from existing in memory. tests still need to be written