Azure Static Webapps is not creating custom authentication

**Describe the bug**

Some well-known configurations are not correctly picked up for auth proxy creation.
Cannot provide it publicly, only in private, but it is a Keycloak OIDC config.

**To Reproduce**
Steps to reproduce the behavior:
1. Deploy the Azure SWA with staticwebapp.config.json like this:
```
{
"routes": [
{
"route": "/*",
"headers": {
"Cache-Control": "no-store"
}
}
],
"auth": {
"identityProviders": {
"customOpenIdConnectProviders": {
"keycloak": {
"registration": {
"clientIdSettingName": "KEYCLOAK_CLIENT_ID",
"clientCredential": {
"clientSecretSettingName": "KEYCLOAK_CLIENT_SECRET"
},
"openIdConnectConfiguration": {
"wellKnownOpenIdConfiguration": ""
}
},
"login": {
"nameClaimType": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name",
"scopes": ["openid", "profile", "email"],
"loginParameterNames": []
}
}
}
}
},
"globalHeaders": {
"Access-Control-Allow-Origin": "*",
"Access-Control-Allow-Methods": "GET, POST, PUT"
}
}

```

`KEYCLOAK_CLIENT_ID` and `KEYCLOAK_CLIENT_SECRET` are correctly set up in Application Settings.
3. Wait for deploy to finish
4. Navigate to .auth/login/keycloak and see a 404 code

**Expected behavior**
Expected to see at least a login page from my keycloak provider

**Screenshots**
From diagnostics:

**Additional context and possible hints**
If I specify the separated auth, token, certs, issuer URLs, I can get a login page but the flows seems buggy and I can't get logged in in the end

**I can provide my SWA URL, tenant and well-known URL for further details in DM**

Thank you