[BUG] API not present in configuration file is still being deployed

### Release version

v6.0.11

### Describe the bug

As per documentation and #435, I was told that I should be able to prevent the deployment of an API by omitting the API from the configuration file.

However, this does not appear to work as I have an API currently commented in configuration code:

```yaml
[...]
apis:
[...]
# - name: api2
# properties:
# serviceUrl: ""
# there is no dev env
```

but the API is being deployed whether I make a publish all artifacts or edit the specs and publish last commit...
I always deploy with configuration file as I have multiple environment, I am using different configuration files for each environment

### Expected behavior

Only API defined explicitly in the configuration files are published. API that are commented should not be published.

### Actual behavior

All API are deployed, all the time.

### Reproduction Steps

configuration file `configuration.d1.yaml`:

```yaml
---
apimServiceName: apimdev01
apis:
#APIs Begin
- name: api1
properties:
serviceUrl: "https://api1.example.net"
# - name: api2
# properties:
# serviceUrl: ""
# there is no dev env
```

folder structure:
- apis
- api1
- apiInformation.json
- specification.json
- api2
- apiInformation.json
- specification.json

Inizia esaminando come viene analizzato configuration.d1.yaml e come il processo di distribuzione seleziona le cartelle sotto apis. Confronta la voce api1 elencata esplicitamente con la cartella api2 non elencata, includendo apiInformation.json e specification.json. Il lavoro è completato quando un’API omessa o commentata nella configurazione non viene distribuita, mentre le API elencate continuano a esserlo.

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