[helm][community] Separate auth config from platform and API

[1cadumagalhaes]

Hello!
We have been using airbyte internally for over a year now. We recently moved our infrastructure and started standardizing. authentication in all platforms.

I understand support for oauth is only on the enterprise edition. But we should be able to deploy the platform (web) without authentication (and use a reverse proxy or simply use a firewall) and still be able to secure the API with basic authorization.

But if we disable auth, the API is completely open, even though it is deployed in a separate service/deployment.

I have made some tests, and it seems like the server "tells" the platform that it should have auth enabled.
I tried configuring it separate by setting the environment variables that are used but looks like it is tightly coupled.
I know that enabling/disabling auth just configures a few auth related environment variables. Not only about enabled but also the values for user and password I think.

Doesnt feel like this is to much to ask or that this would conflict with the company's interest, since this would basically be an advanced way of deploying it, while also enabling users to take control over how they use it. Also, enterprise would still come with built in oauth support and keycloak.