[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.

Comienza reproduciendo el despliegue con una API denominada value respaldada por un Azure Key Vault inaccesible, comparando las rutas del publisher de GA y ADO. Rastrea la creación de named values y el manejo de errores en el flujo de trabajo del publisher. Se considera terminado cuando GA informa del fallo de acceso a Key Vault y se detiene antes de intentar configurar la policy dependiente.

Escrito por el modelo de indexación a partir del texto del issue.