Parasail: https://github.com/jeffdaily/parasail

It's faster than the pairwise sequence algorithms we have in
OpenStructure. However, the main reason to check out another solution
is the fact that OpenStructure may return suboptimal alignment
results. This is a result of how the dynamic programming table is built.
If for a certain cell in the dynamic programming table a match state and
insertion state score equally, match is preferred. There is a chance
that we would get a better score later on if we would stick with the
insertion state (gap open penalties vs. gap extension penalties).
Not sure if this will be fixed in the near future.

Numpy support in C++ enabled features at two points:
Efficient way of setting positions in entity handles or setting meshes
in gfx.PrimList.

Support for newer numpy versions would've required an effort to implement.
As far as I know, no one uses these features (fingers crossed) so let's just
dump numpy alltogether to simplify the build system.

This updates the module versions to match the versions we currently use
for the OST module on sciCORE.

This sets up the compound lib upon calling import ost.
It simplifies the ost_startup.py script accordingly.
It is now possible to override the compound lib with
an environment variable: OST_COMPOUNDS_CHEMLIB

Versions are updated to what the mighty Schwede lab uses in production

Compilation was broken for years when IMG has been disabled.
IMG is now always built.

You might have to adapt CMake flags when building OpenStructure to variables specified here:
https://cmake.org/cmake/help/latest/module/FindPython.html

First entry is about adding the -pthread flag to resolve linking
problems. Has been observed on the scicore cluster and reported
by Yuri (FreeBSD 12.2).

As weird as it sounds but the proper var. to set is PNG_PNG_INCLUDE_DIR instead
of PNG_INCLUDE_DIR. The latter is overwritten by FindPNG and actually obsolete
(see https://github.com/Kitware/CMake/blob/master/Modules/FindPNG.cmake).