[BUG]Removal of subscription Folder from Artifacts Deletes All Subscriptions in APIM Instance

### Release version

v6.0.1.1

### Describe the bug

It has been observed that when the subscription folder is removed from the artifacts, it results in the deletion of all subscriptions present in the Azure API Management (APIM) instance. This is a critical issue because it leads to unintended loss of subscriptions and disrupts the management of API access.

Impact:
Data Loss: Loss of all subscriptions in the APIM instance can lead to significant disruptions in service and access control.
Configuration Management: Failure to override values from the .yaml file can result in inconsistent and unexpected behavior.

kindly provide the solution.

### Expected behavior

Removing the subscription folder should not affect existing subscriptions in the APIM instance. Instead, the process should handle this folder appropriately without deleting existing data or should provide a warning about potential impacts.

### Actual behavior

The removal of the subscription folder leads to the deletion of all existing subscriptions in the APIM instance.
Additionally, the configuration values from the configuration..yaml file are not being overridden as expected.

### Reproduction Steps

Remove the subscription folder from the artifacts directory.
Deploy the artifacts to the APIM instance.
Observe that all existing subscriptions in the APIM instance are deleted.

Reproduzieren Sie das Problem, indem Sie den subscription-Ordner aus dem artifacts-Verzeichnis entfernen und auf der Azure API Management-Instanz deployen. Vergleichen Sie die resultierenden subscriptions mit dem erwarteten Verhalten und untersuchen Sie, wie die Werte in configuration..yaml angewendet werden; abgeschlossen ist die Aufgabe, wenn bestehende subscriptions intakt bleiben und die Konfigurationsüberschreibungen wie erwartet funktionieren.

Vom Indexierungsmodell aus dem Issue-Text verfasst.