DomainID or DomainName validation is inconsistent

Nessuno ha ancora preso questa issue.

#### Overview of the Issue

Using hashicorp/packer container with a HCL file that contains `token`:
- Setting `domain_id` (without `domain_name`) ask to remove it because is not required while using `token`
- If neither `domain_name` or `domain_id` is used then error asking for one of them
- If neither `domain_name` or `domain_id` is used but `OS_DOMAIN_ID` env var exported then is OK

#### Reproduction Steps

```
packer validate test.pkr.hcl
````

If `domain_id = "default"` + `token = '...'` then:
```
packer validate vault-raft.pkr.hcl
Error: 1 error(s) occurred:
* DomainID may not be provided when authenticating with a TokenID
on vault-raft.pkr.hcl line 1:
(source code not available)
```

If `#domain_id = "default"` = `token = '...'` then:
```
Error: 1 error(s) occurred:
* You must provide exactly one of DomainID or DomainName in a Scope with ProjectName
on vault-raft.pkr.hcl line 1:
(source code not available)
```

If `#domain_id = "default"` = `token = '...'` + `export OS_DOMAIN_ID=default` then:
```
The configuration is valid.
```

### Plugin and Packer version

```
packer version
Packer v1.8.0
```

### Simplified Packer Buildfile

`test.pkr.hcl` file:

```
source "openstack" "hello" {
#domain_id = "default"
token = "TheRealTokenWasHere"
identity_endpoint = "https://auth.cloud.ovh.net/v3"
image_name = "debian-hello-test"
source_image_name = "Debian 11"
flavor = "s1-2"
tenant_name = "TheTenantNameWasHere"
region = "GRA7"
ssh_username = "debian"
networks = ["TheNetworkIdWasHere"]
}
build {
sources = ["source.openstack.hello"]
provisioner "shell" {
execute_command = "sudo -S sh -c '{{ .Vars }} {{ .Path }}'"
scripts = fileset(".", "scripts/{install,secure}.sh")
}
}
```

### Operating system and Environment details

Docker image `hashicorp/packer` running in GitlabCI runner ignoring the entrypoint

Also tested in a Debian 11 laptop running the same Packer version.

Riproduci il comportamento di validazione con il test.pkr.hcl fornito usando packer validate, confrontando i casi domain_id, domain_name, token e OS_DOMAIN_ID. Traccia il punto di ingresso della validazione che produce i due errori in conflitto e aggiungi o aggiorna la copertura per queste configurazioni. Il lavoro è completato quando configurazioni equivalenti ricevono risultati di validazione coerenti e corretti.

Scritto dal modello di indicizzazione a partire dal testo della issue.