feat: make conditional ui available via env var in quickstart

[like-a-bause]

Description

Adds the ability to set experimental feature conditional ui in quickstart

Implementation

Tests

Todos

Additional context

[bjoern-m]

Just to be sure, is it intended that the value of HANKO_ENABLE_CONDITIONAL_UI is discarded? So when I set HANKO_ENABLE_CONDITIONAL_UI=false it's okay that conditional UI is enabled anyway, because it's just a "flag"?

[like-a-bause]

Just to be sure, is it intended that the value of HANKO_ENABLE_CONDITIONAL_UI is discarded? So when I set HANKO_ENABLE_CONDITIONAL_UI=false it's okay that conditional UI is enabled anyway, because it's just a "flag"?

Yes. I thought of it as a boolean flag. But I don't have a strong opinion about that. We could also handle this as "must explicitly be set to true".

[bjoern-m]

Just to be sure, is it intended that the value of HANKO_ENABLE_CONDITIONAL_UI is discarded? So when I set HANKO_ENABLE_CONDITIONAL_UI=false it's okay that conditional UI is enabled anyway, because it's just a "flag"?

Yes. I thought of it as a boolean flag. But I don't have a strong opinion about that. We could also handle this as "must explicitly be set to true".

Ok, me neither, but I think we should create a task to mention the available environment variables in the quickstart README.