Allow augur to optionally recieve augur db connection parameters as individual components

[MoralCode]

To enable cloud-native deployment (see https://github.com/oss-aspen/augur-on-ocp) with the CrunchyData Postgres operator (which provides database connection information as individual values), A wrapper is likely needed around the flower container to add some custom logic nearly identical to that in #3222, allowing the connection string to be either provided as a single string, or as separate values.

[OadeO6]

Hi @MoralCode 👋

I'd love to work on this as my first contribution! However, I noticed that Flower uses the same entry point as the Augur backend. The update in #3222 should address this issue as well.

I’d be grateful if you could provide more details in case the required fix goes beyond what #3222 covers.

[MoralCode]

Ah yes i see what you are saying. The issue here is that there should be the option to pass the DB connection parameters into the augur backend image. This is because the CrunchyDB postgres operator provides individual secrets and passing them into augur is going to be much easier if theres an option to pass them in individually as an option in addition to the single AUGUR_DB env var for the entire connection string.

This issue stems from the fact that this part of the augur-on-ocp repo is essentially a hardcoded secret compared to other places in the code where this is simply saying "use the value at the key provided by the crunchy operator"

Does that help?