Ignoring values passed in `env` in Azure DevOps pipeline. It sends all values defined in `Variables`

**Describe the bug**

As said in the documentation, in order to pass environment variables to ASWA through Azure DevOps pipeline, they should be declared in `env` field (https://docs.microsoft.com/en-us/azure/static-web-apps/build-configuration?tabs=github-actions#environment-variables)

However, `env` field is currently being ignored, and the pipeline passes all the variables declared in `Variables`

**To Reproduce**

```
- task: AzureStaticWebApp@0
displayName: Release to ASWA
inputs:
app_location: 'build' # App source code path relative to cwd
api_location: 'api' # Api source code path relative to cwd
skip_app_build: true
azure_static_web_apps_api_token:
env:
MY_ENV_VAR: 1234
```
In `Variables` create other env variable

If you try to load both `MY_ENV_VAR` and `OTHER_ENV_VAR` from your static web app, you will notice that only OTHER_WEB_APP has been properly set

**Expected behavior**
The yml task should consider only environment variables defined in `env` field, regardless of variables created in `Variables`.