Simplify components versions files duplication

[sbesson]

See #2253

Two separate files seem to hardcode the set of component versions and need to be maintained in sync. I assume only one of them is effectively in use and we could reduce the maintenance burden?

[jburel]

The workflow is as follows:

• omero/autogen_docs is run
• one step in the script does the following omero/autogen_db_version.py $WORKSPACE/OMERO.server > omero/conf_autogen.py
• conf_autogen.py is then used in conf.py to access the version number

[sbesson]

So should these files have been updated as part of #2252 ?

[jburel]

partially. The DB version will be the one that could have been modified but no change this time in DB version.
The rest is hard-coded
We will need something like
ome/openmicroscopy#6329 in order to change the values

[jburel]

I remember now having to add

print('version_omero_server = "5.6.5"')
print('version_bioformats = "6.10.0"')
print('version_blitz = "5.5.12"')
print('version_server = "5.6.4"')
print('version_romio = "5.7.0"')
print('version_renderer = "5.5.10"')
print('version_common = "5.6.7"')
print('version_model = "5.6.7"')
print('version_gateway = "5.6.10"')
print('version_insight = "5.7.0"')
print('version_matlab = "5.5.4"')
print('version_dsl_plugin = "5.5.2"')
print('version_blitz_plugin = "5.5.2"')
print('version_ice_builder = "1.5.2"')
print('version_py = "5.11.2"')
print('version_web = "5.14.1"')
print('version_dropbox = "5.6.2"')

to keep the workflow and the links working after the split.

[jburel]

Option to update the dependencies as part of the scheduled daily build
See #2258