Duplicate configuration entries across configuration files (v6/k8s) for database access.

[hcadavid]

Duplicated configurations and error-prone conventions were put in place to give the Job PODs access to the database files. This should be improved.

First, each database file path is duplicated on the vantage6 config file:

v6-on-kubernetes-PoC/integration_poc/configs/node_legacy_config.yaml

Lines 61 to 64 in faeab98

	databases:
	- label: default
	uri: /home/hcadavid/k8s/v6-on-kubernetes-PoC/csv/employees.csv
	type: csv

And on the node's volume path set on the node's YAML config file:

v6-on-kubernetes-PoC/integration_poc/kubeconfs/node_pod_config.yaml

Lines 61 to 63 in faeab98

	- name: v6-node-default-database
	hostPath:
	path: /home/hcadavid/k8s/v6-on-kubernetes-PoC/csv/employees.csv

Given that the mountPaths (on the POD/Container) also defined on the node's YAML file for these volumePaths are unknown by the v6-node, there is no way to inform the PODs which path they should use. As a provisional work-around, a convention was introduced: the mount path will always be /app/.databases/ followed by the same path on the host:

v6-on-kubernetes-PoC/integration_poc/kubeconfs/node_pod_config.yaml

Lines 48 to 49 in faeab98

	- name: v6-node-default-database
	mountPath: /app/.databases/home/hcadavid/k8s/v6-on-kubernetes-PoC/csv/employees.csv

This may not require to be addressed if 'Sessions' in v6 remove the need for passing these values to the nodes.