This is likely to fail if we don't have the right mounts...

This test was relying on a "bad" alignment between two essentially
unrelated chains. This is no longer happening after the replacement of
GlobalAlign by SemiGlobal in commit ddfa2ab5, and the chains no longer
align meaningfully. As a result no residue names were mismatching, as
the representation of the binding site in the model no longer existed.

We removed this assumption and only replace a single residue in the
entity. This avoids depending on an alignment in this test.

Terminal residues can be weird in GlobalAlign. E.g.

AAABAAB
AAA---B

instead of

AAABAAB
AAAB---

SemiGlobalAlign produces the latter

Before it just complained that the compound library was created with
an unsupported version of OST while in fact it could have been an empty or
even random file. Now it says:
Exception: Could not read OST version from loaded SQLITE DB - no valid
CompoundLib

required by prody/biotite

Reduces insane amount of compiler warnings. Inheritance from std::iterator
template was used to define traits of an iterator. Cool people define these
traits directly nowadays.

That's the minimum length for a peptide chain to be considered in chain
mapping

DOD is water too! This must be written in the chem_comp category.
Otherwise we're ending up with an invalid mmcif file. Instead of
just hardcoding, we now add whatever monomer id we observe in any
of the residues.

For predictable behaviour, providing MMCifWriterEntity objects has
the following restrictions now:

- Only allow MMCifWriterEntity of type polymer
- All chains in ent that are of type polymer must be assigned
  to exactly one of these entity_info objects and must match the SEQRES
  (MMCifWriterEntity::mon_ids)
- All chain names that are assigned to entity_info must be valid chains
  in ent

Until now, the actions were failing with somewhat cryptic messages
raised from arbitrary locations. This one should be more user-friendly.

CreateBU always returns a valid entity. We already check if it's empty
separately.

This is made possible now that we have a CreateBU function.

It turns out for some reason we were reading them from chains, based on
the ChainType of the chain. This prevented extracting anything from
legacy PDB files and didn't match the documented behavior in the action.

Now extraction is based on the IsLigand flag only, and documentation is
consistent throughout. Behavior on PDB files is tested.