Add Lightfuzz (Draft)

[liquidsec]

For now, a placeholder to assist in keeping the lightfuzz branch synced with changes to dev until it's ready

• Body Parameters (new type, xml / JSON)
• SSRF Submodule (on hold)
• Documentation
• Add comments to all lightfuzz submodules explaining detection logic, etc
• override logging to automatically prepend lightfuzz submodule to messages
• add portfilter module to all lightfuzz presets
• Answer the question - deadly module or not?

Other TODOs:

• Make lightfuzz into a folder
• Reduce duplicate code in excavate (emission of WEB_PARAMETER)

@TheTechromancer follow up on:

• Autogenerating documentation for lightfuzz modules based off their docstrings/metadata (similar to BBOT modules)
• Necessity of using acorasick python library over yara

[liquidsec]

@TheTechromancer
"Necessity of using acorasick python library over yara"

As i've explained before, the overhead for building these using yara means for these small quick checks its actually MUCH faster. We really dont want to be compiling yara rules constantly. The existing stuff we do with yara involves compiling them once at the beginning of the scan, which is expensive but obviously well worth it as they are used for the life of the scan. This current string_scan implementation is working great.

Package overhead of ahocorasick is minuscule, if we're looking to lean things up there are much better choices.