Use the same config file for both the importer and efsity tools

[Wambere]

When setting up a new project, you need to use the importer to setup keycloak/create users/upload content, then you need to use efsity to validate and publish configs. At the moment the importer uses a config.py file for configs while efsity uses an env.properties file, both of which have more or less the same content. Is it possible to just have one env file and use it for both?

[pld]

makes sense, probably easier to have the importer use the env.properties since Java is (imo) more picky about paths

[FikriMilano]

would it be a good idea to have the env.properties in the root level of the repo then? i.e. the same level as these folders and files.
if so, the todo would be to:

1. create the env.properties file in the root level
2. migrate importer and efsity tool to get configs from this root level env.properties (other tools might follow?)

[Wambere]

@FikriMilano for this I think we'd want to use a .env file instead of the env.properties
The importer has already been updated to use .env so this change needs to happen to efsity
And yes, it definitely makes sense to have it at the root level