Allow to skip the winery database initialization by configuration

It works well in an interactive job because it's executed on a login node that have access to internet.

However, when the job is launched in an sbatch job, it stays blocked because the initialization script can't be retrieved.

Given there is no command line tools (AFAIK) to create the db, maybe this could be made optional by configuration to not be a blocker when the db is already initialized