feat: complex configuration can be supplied as yaml

[dhhyi]

PR Type

[x] Feature

What Is the Current Behavior?

Complex configurations for IDENTITY_PROVIDER or TACTON have to be supplied as JSON to the deployments:

  IDENTITY_PROVIDERS: |
    { "Auth0": { "type": "auth0", "domain": "dev-asdf1234.eu.auth0.com", "clientID": "012ea8f1db7a838b65a8b29e8464742166877abb" } }

When trying to structure the data, it becomes very verbose and even then JSON parsing is very sensitive to commas and quotes and therefore prone to error:

  IDENTITY_PROVIDERS: |
    { 
      "Auth0": { 
        "type": "auth0",
        "domain": "dev-asdf1234.eu.auth0.com",
        "clientID": "012ea8f1db7a838b65a8b29e8464742166877abb"
      }
    }

What Is the New Behavior?

Complex configuration can be supplied as YAML:

  IDENTITY_PROVIDERS: |
    Auth0:
      type: auth0
      domain: dev-asdf1234.eu.auth0.com
      clientID: 012ea8f1db7a838b65a8b29e8464742166877abb

Does this PR Introduce a Breaking Change?

[ ] Yes
[x] No

Other Information

Depends on integration of #1080, so that js-yaml is only included into the server bundle.

AB#78387