Keep history of ruleset changes

[matthias-ronge]

Is your feature request related to a problem? Please describe. When system responsible persons with yet less knowledge, and probably without an XSD-capable editor, edit the ruleset, this sometimes results in a not well-working ruleset (either technical, or by behavior). Giving support, it is sometimes later hard to tell which changes have been made.

Describe the solution you'd like Production should store a hash of the ruleset in the database. When it encounters a modified ruleset, it should make a copy of it, so to create a editing history.

Describe alternatives you've considered Using git in some way? A ruleset validator and/or a ruleset editor would be other nice options, but they should make it to separate issues.

Additional context If a ruleset.xml is first used, a copy is created as ruleset.xml.1. If the hash value changes, a new copy is made as ruleset.xml.2 etc.