Be able to set env variables retrieved from secrets in the `env` section instead of using `export`

[PabloZaiden]

Currently, there are several jobs that retrieve secrets from key vault and later set them as environment variables for other steps.

The issue is that right now the script that retrieves the values adds double quotes surrounding the retrieved values. That has the side effect of not being able to set the environment variables directly in the env section of the steps and having to write export mySecret=${{...}} inside the script.

When retrieving secrets, they should be returned without double-quotes so they can be used in both scenarios.