Fix/complete rule element support

[Seblat5ch]

Summary

Adds complete rule element support for parsing Outlook 2019 .rwz files with all conditions, actions, and exceptions per the RWZ Format Specification.

The original parser only handled ~15 element types and crashed on unknown IDs. This update adds support for all documented element types, enabling successful parsing of real-world .rwz files.

Changes

• Added 15 missing data type classes: ImportanceRuleElementData, SensitivityRuleElementData, CategoriesListRuleElementData, PathRuleElementData, DisplayMessageInNewItemAlertWindowRuleElementData, FlagRuleElementData, DeferDeliveryRuleElementData, PerformCustomActionRuleElementData, AutomaticReplyRuleElementData, RunScriptRuleElementData, FlagForFollowUpRuleElementData, ApplyRetentionPolicyRuleElementData, OnThisComputerOnlyRuleElementData, SizeInSpecificRangeRuleElementData, ReceivedInSpecificDateSpanRuleElementData, FormTypeRuleElementData, ThroughAccountRuleElementData, SenderInSpecifiedAddressBookRuleElementData
• Fixed incorrect action-to-data-type mappings (e.g. 0x139 "move a copy" was SimpleRuleElementData, should be MoveToFolderRuleElementData)
• Added all exception element cases (0x1F4-0x21B) — these were completely missing
• Fixed RuleHeader separator logic for last rule (no separator per spec)
• Fixed FlaggedForActionRuleElementData to properly read Extended + Reserved + actionName (was empty class)
• Replaced hard assertions with softAssert for graceful error handling
• Made input file path configurable via CLI argument (process.argv[2])

Testing

Successfully parsed an Outlook 2019 .rwz file containing 137 rules with 0 errors.

[hughbe]

Hey @asklar just wondering if you encountered any problems with the specification when you made this? I'm keen to make sure it's accurate