Add Mplog-Parser to parse Windows Defender MPLog

[Qazeer]

Description

Add Mplog-Parser module to parse Windows Defender MPLog files.

As a side note, it would be useful to have a %sourceFileDirectory% variable for case like this one, as the tool takes into parameter a folder but does not recursively process it. The variable would return the directory path of file(s) that match a FileMask. It would have a few benefits, including the support of piping a target collection directly as the module source (without having to manually add the drive letter to the module source), and allow processing of multiple folders that might contain MPLog files (in addition to the default location).

Checklist:

Please replace every instance of [ ] with [X] OR click on the checkboxes after you submit your PR

• I have generated a unique GUID for my Target(s)/Module(s)
• I have placed the Target(s)/Module(s) in an appropriate subfolder in Targets or Modules. If one doesn't exist, I have either added it to the Misc folder or created a relevant subfolder with justification
• I have set or updated the version of my Target(s)/Module(s)
• I have verified that KAPE parses the Target(s)/Module(s) successfully via kape.exe, using --tlist/--mlist and corrected any errors
• I have validated my Target(s)/Module(s) against test data and verified they are working as intended
• I have made an attempt to document the artifacts within the Target(s) or Module(s) I am submitting. If documentation doesn't exist, I have placed N/A underneath the Documentation header
• For Modules, I have consulted either the Module Guide, Module Template, Compound Module Guide, or Compound Module Template to ensure my Module(s) follow the same format

[AndrewRathbun]

Looks very useful!