[WFLY-20915] Remove bitnami's postgresql Helm Chart

[jmesnil]

Instead, the DB is deployed directly by the Helm Chart

Update the wildfly Helm chart to actually pulls the DB credentials from the config map (as stated in the doc) instead of hard-coding them in the values.yaml file.

This fixes https://issues.redhat.com/browse/WFLY-20915

[emmartins]

@jmesnil I am going to delegate the review to the owner and tester, but before I do that please update the README-source.adoc instead of the README.adoc, the latter is just a flattened version of the former, built automatically by a workflow

[jmesnil]

The README-source.adoc does not require any changes, they were done in the ancillary .adoc files.
Should I remove the changes in README.adoc or is there a step to generate it before I commit it?

[emmartins]

The README-source.adoc does not require any changes, they were done in the ancillary .adoc files. Should I remove the changes in README.adoc or is there a step to generate it before I commit it?

I see, that's ok then, you can keep it, it will - at most - be rebuilt and updated after

[emmartins]

@jmesnil do we still need this unique (in the context of quickstarts) design of Charts.yaml + values.yaml , or could we also switch to the common design of all other quickstarts, with charts/helm.yaml ? This would allow us to fully reuse the shared-docs content related with Helm charts.
Also I think the docs could be much improved...
Anyway ^^ is not new and can be worked out in separated, the priority now is to definitely fix the bitnami issue, approving!

[jmesnil]

@emmartins We still need this structure as we are deploying a PostgreSQL resource in addition to the WildFly resources.