fix: destination network creation
When dst network is created (not found), the returned dict does not have
subnets attribute initialized. That may cause issues in later stages,
where we rely on at least one subnet_id being present (see
describe_server_network_connection function).
Fixed by getting the network from OStack again, after everything has been created.
See failed pipeline:
- Dst network without subnet
- Error later in execution
- Final assertion error