UniProt version is not taken into account of required database

[pverscha]

At this moment, the application does not support to construct custom databases from UniProt-versions different from the most recent version. This means that the specific UniProt version that's configured for a CustomDatabase is not taken into account when constructing this new custom database. Users cannot choose which UniProt version should be used when building a database at this time, but if they choose to process a sample that's configured with an older version of UniProt they might stumble upon this.

This issue is a consequence of the fact that parsing and processing older UniProt versions is not yet supported by the application at this point in time (this will normally be fixed in a future release).