(MODULES-6129) negated option with address mask bugfix

[mirekys]

This fixes the issues with rules in the following format (e. g. used by Docker),
where exclamation mark precedes an option followed by outiface:

"-A FORWARD -i br-123456 ! -o br-123456 -j ACCEPT"

Without the fix, it is being parsed like this:

# we do a similar thing for negated address masks (source and destination).
values = values.gsub(/(-\S+) (!)\s?(\S*)/,'\1 "\2 \3"')
#=> "-A FORWARD -i br-123456 \"! -o\" br-123456 -j ACCEPT"

# the actual rule will have the ! mark before the option.
values = values.gsub(/(!)\s*(-\S+)\s*(\S*)/, '\2 "\1 \3"')
#=> "-A FORWARD br-123456 \"-o\" \"! br-123456\" ACCEPT"

Which, in the end, results in:

values = ["ACCEPT", "\"! br-123456\"", "\"-o\"", "br-123456", "FORWARD"]
keys = [:jump, :iniface, :chain]
Error: Failed to apply catalog: Parser error: keys (3) and values (5) count mismatch on line: -A FORWARD -i br-123456 ! -o br-123456 -j ACCEPT

The simple solution is to switch those two gsubs, so it shifts the ! behind option first and only then it quotes the ! together with an option argument (e.g. outiface):

values = values.gsub(/(!)\s*(-\S+)\s*(\S*)/, '\2 "\1 \3"')
#=> "-A FORWARD -i br-123456 ! -o br-123456 -j ACCEPT"

values = values.gsub(/(-\S+) (!)\s?(\S*)/,'\1 "\2 \3"')
#=> "-A FORWARD -i br-123456 -o \"! br-123456\" -j ACCEPT"

A value in this format is then picked up by the parser correctly.