Bug 1628278

Description of problem:
Option --check-config of firewall-cmd should check validity of rules located inside .xml files, but it seems that it is struggling when checking rich rules.
When valid rich rule is added via command and address is invalidated manually inside .xml, --check-config should throw error, when it finds invalid address, but it returns success.
Check should return same error as error returned by command, where invalid address is written directly in the command.

Version-Release number of selected component (if applicable):
firewalld-0.5.3-5.el7

How reproducible:
everytime

Steps to Reproduce:
1. Add valid rule:
firewall-cmd --permanent --zone=public --add-rich-rule='rule family="ipv4" source address="192.168.1.1" service name="tftp" log prefix="tftp" level="info" limit value="1/m" accept'
2. Manually change address "192.168.1.1" to something invalid (e.g.: 192.abc.invalid.1 ) inside /etc/firewalld/zone/public.xml
3. Run command:
firewall-cmd --check-config

1. Same for family="ipv6" and providing invalid ipv6 address (e.g.: 3001::2::2::7334)

Actual results:
success

Expected results:
Option --check-config should throw error: INVALID_ADDR, when invalid address exists in rich rule inside xml just as throws error when the rule is added via command (e.g.: 
firewall-cmd --permanent --zone=public --add-rich-rule='rule family="ipv4" source address="invalid.ipv4.address" service name="tftp" log prefix="tftp" level="info" limit value="1/m" accept'
)

Additional info:
Adding invalid rule manually:
firewall-cmd --permanent --zone=public --add-rich-rule='rule family="ipv6" source address="2001::8a20::7334" service name="tftp" log prefix="tftp" level="info" limit value="1/m" accept'
Error: INVALID_ADDR: 2001::8a20::7334
Throws error as expected.