Add YML configuration parsing

[alexkiro]

We should add a new configuration mode for parsing rules that is more easily parsed and is a standing standard YML, e.g. a GTUBE rule:

body GTUBE      /XJS\*C4JDBQADN1\.NSBN3\*2IDNEN\*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL\*C\.34X/
describe GTUBE  Generic Test for Unsolicited Bulk Email
score GTUBE     1000

Would become:

GTUBE:
 type: body
 value: /XJS\*C4JDBQADN1\.NSBN3\*2IDNEN\*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL\*C\.34X/
 score: 1000
 desc: Generic Test for Unsolicited Bulk Email

---

• This should generate the results dictionary that we generate in the parser that is required by the ruleset
• This should also cover the configuration options an all of its types
• A script should be created that converts the old configuration into the new YML version
• Before the configuration is parsed as an YML file we should interpolate it as a Jinja Template to cover cases where {% if commands are involved (similar to what SA has)
• The exiting system should still be in place so the parse should determine if it is required to parse it in the old format instead of the new format
• All tests should be ran under both types of configurations and the converter script should be used to change from the old config to the new one (similar to what we do with the compile script now and the USE_PICKLES flag.