[BUG] Publisher not throwing error in GA workflows when connectivity is not available

### Release version

v6.0.1.1

### Describe the bug

When publisher run for the artifacts having named values attached to Azure Keyvault, during publisher run if AKV is not accessible or have no proper rights ADO throws an error clearly stating the same but GA doesn't fail and go ahead without any error.

### Expected behavior

GA also should fail when there is no Access to the respective resource like ADO does.

### Actual behavior

GA does not fail when connectivity is not available and logs says it has put the named values in APIM but actually it is not created. At the same time ADO works fine and give proper error.

### Reproduction Steps

1. Create an api has reference to namedvalue which holds the value from the Keyvault.
2. Deploy to another instance which does not have access to the Kwyvault.
3. Run publisher.
4. In GA you can see it will not fail for the named value but fail when it will try to setup the policy as named value object is not created and it is trying to refer the same. And when you run the same using ADO it will fail at the stage of named value creation itself.

Commencez par reproduire le déploiement avec une API nommée value, adossée à un Azure Key Vault inaccessible, en comparant les chemins du publisher de GA et d’ADO. Suivez la création des named values et la gestion des erreurs dans le workflow du publisher. C’est terminé lorsque GA signale l’échec d’accès à Key Vault et s’arrête avant de tenter de configurer la policy dépendante.

Rédigé par le modèle d'indexation à partir du texte de l'issue.