If there are no networks in project, packer just moves on

When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.

#### Overview of the Issue
If there are no networks in project, packer just moves on next step, creates volume, image, and try to connect to server without interfaces.
#### Reproduction Steps
Remove all network from openstack
Remove network id, cidr, any info about network in buildfile

### Plugin and Packer version

From `v1.0.1`

### Simplified Packer Buildfile

source "openstack" "test-1" {
flavor = var.flavor
identity_endpoint = var.identity_endpoint
image_disk_format = "raw"
image_name = "${local.image_name}"
image_tags = ["packer"]
region = "region"
source_image_name = var.source_image_name
ssh_clear_authorized_keys = true
ssh_username = "root"
use_blockstorage_volume = true
},
build {
sources = [
"source.openstack.test-1",
]
}

### Operating system and Environment details

### Log Fragments and crash.log files

2022-12-08T18:42:34+03:00: ==> openstack.test-1: Loading flavor: m1.tiny
2022-12-08T18:42:35+03:00: openstack.test-1: Verified flavor. ID: 1
2022-12-08T18:42:35+03:00: ==> openstack.test-1: Creating temporary RSA SSH key for instance...
2022-12-08T18:42:37+03:00: ==> openstack.test-1: Creating temporary keypair: packer_639205ea-c1ed-6490-cd4c-6e24092f53fd ...
2022-12-08T18:42:38+03:00: ==> openstack.test-1: Created temporary keypair: packer_639205ea-c1ed-6490-cd4c-6e24092f53fd
2022-12-08T18:42:38+03:00: openstack.test-1: Found Image ID: 56eeddc3-d88b-4138-84b8-2cd728419d47
2022-12-08T18:42:39+03:00: ==> openstack.test-1: Creating volume...
2022-12-08T18:42:40+03:00: ==> openstack.test-1: Waiting for volume packer_639205ea-4806-247b-2ee9-12f349cd4c3d (volume id: 2f9301b5-9b5f-4064-9435-daf0583ec3df) to become available...
2022-12-08T18:42:42+03:00: openstack.test-1: Volume ID: 2f9301b5-9b5f-4064-9435-daf0583ec3df
2022-12-08T18:42:42+03:00: ==> openstack.test-1: Launching server...
2022-12-08T18:42:42+03:00: ==> openstack.test-1: Launching server...
2022-12-08T18:42:48+03:00: openstack.test-1: Server ID: 97703c5d-e66e-44a7-82e5-46d3b0720ed6
2022-12-08T18:42:48+03:00: ==> openstack.test-1: Waiting for server to become ready...
2022-12-08T18:42:57+03:00: openstack.test-1: Floating IP not required
2022-12-08T18:42:58+03:00: ==> openstack.test-1: Waiting for SSH to become available...
2022-12-08T18:47:58+03:00: ==> openstack.test-1: Timeout waiting for SSH.
2022-12-08T18:47:58+03:00: ==> openstack.test-1: Timeout waiting for SSH.
2022-12-08T18:47:58+03:00: ==> openstack.test-1: Step "StepConnect" failed

Der relevante Einstiegspunkt ist der OpenStack-Builder-Ablauf, der StepConnect erreicht; beginne damit nachzuverfolgen, wie eine leere Netzwerkkonfiguration vor dem Start des Servers behandelt wird. Reproduziere den Build ohne Netzwerk mithilfe der bereitgestellten Konfiguration und Logs und füge anschließend einen fokussierten Regressionstest hinzu, der zeigt, dass dieser Fall explizit behandelt wird, anstatt mit einem SSH-Timeout fortzufahren.

Vom Indexierungsmodell aus dem Issue-Text verfasst.