Add SCION compiler output checks

[amdfxlucas]

SEED is in dire need for a means to check if the generated output is consistent.
For large simulations this can save a lot of time spent on building docker images which eventually turn out to misconfigured and dysfunctional.

In the case of a SCION simulation this comes down to checking if the contents of 'docker-compose.yml' ( where SCION border-routers map to 'brdnode_xyz' services and are assigned an 'ip_v4_address' on the IX or XC network i.e. 'net_ix_xyz')
match the contents of the 'topology.json' files for each AS (where under the 'border_routers' key for each AS interface under 'underlay' the internal IP address is given ).

If nodes have from their 'topology.json' file the wrong IP addresses of border routers, the log files of the SCION distributables will contain strange 'UDP socket i/o read timeout' errors which are extremely hard to make sense of. You really want to avoid to ever find yourself in this situation.

[martenwallewein]

Thank for bringing this up! Looks good to have this check to ensure everything is configured correctly, but wouldn't it make more sense to fix the root cause? Or is there no root cause why sometimes IPs are not correct?