An Operator might create their own network-data in order to provide some custom information.

While this is fully supported, it may happen the actual "name" value is changed (typo, or will to change it). This will then create unexpected issues due to the amount of checks done against the "network.name" within tripleo-heat-templates and related tools.

The goal here is to raise two kind of things, depending on what is found in the network-data:

- a simple warning if the only missing networks are InternalApi or Storage (in such case, the ctlplane is used)
- a hard stop if any of the other default networks (StorageMgmt, Tenant, External) is missing

That should prevent some headaches and support cases, while adding some more confidence when we go down the "custom network" path.

This can be a proper validation provided by tripleo-validations, and called as an OC deploy preflight check.