We forgot to include the description extractor in the totals. Also,
it said batch jobs were excluded from the totals, which is not the
case.

This enables attachement of these handlers to elements that are
added to the DOM later as opposed to being in the original source
HTML.

The alternative variant protein sequence translated from a
non-reference start codon (created by the variant), was not
color-diffed as normal variant protein sequences are.

In the process we also rename the `oldprotein` and `newprotein`
fields in the output object to `oldProtein` and `newProtein` to
be more consistent with other field names.

Adds a `EXTRACTOR_MAX_INPUT_LENGTH` configuration setting, defaulting
to 50 Kbp.

Fixes #43

This is hopefully a temporary measure. At the moment we cannot accurately
predict the running time of the extractor, so we have to aggressively
limit the input based on the worst-case expectation.

As a worst-case scenario, we currently use random input sequences, where
length 1000bp yields about 500ms of running time.

In the future we hope to either:

1. Predict the running time and abort if needed.
2. Keep track of the running time and abort if needed.
3. Run the extractor in a task scheduler with a running time limit.

Jeroen F.J. Laros authored 9 years ago and Vermaat committed 9 years ago

We can now compare two sequences by supplying their sequence strings,
accession numbers, or uploaded file.

This is a work in progress as there still seem to be some bugs. For example,
some unit tests fail due to incorrect descriptions generated and others fail
due to a crash.

Fixes #24