Clean unused database properties from generated values.yaml

[filippomc]

Properties for databases are specified even if no database is selected. We this we want to remove the useless specifications when they are not needed

[aranega]

When no database is used, should the configuration still own an empty entry for database?

Like, the values.yaml file should contains:

• an empty database entry --> database: {} ?
• a database entrty with a name and nothing else --> database: {name: appname-db} ?
• no database entry ?

Also, writing tests I saw that even if I remove the entries from the helm_values during the process, some are added back by the HarnessMainConfig at the end.
This is not a problem for the deployment/values.yaml generation as the file generation is performed before the instance of HarnessMainConfig is created.
However, in the deployment directory, there is still some artifacts from others db that are here.
For example, if I have a project with no db, I still have deployment/files/db-mongo-backup.sh which is generated, as well as a lot of templates files in deployment/templates.
Should they be removed also?