Abulafia

Fixes a problem in `actions/__init__.py` which imported the deprecated `Verify` class. Small updates to tests for the task interface.

- A massive update and overhaul of documentation, which can be now found under [examples](https://github.com/thiippal/abulafia/tree/main/examples).

This release includes several breaking changes:

- The following pre-defined interfaces have been removed: `AddOutlines`, `LabelledSegmentationVerification`, `FixImageSegmentation`, `MulticlassVerification` and `LabelledSegmentationVerificationNoCheckbox`.
- The same functionalities are now implemented in fewer interfaces with additional components that may be invoked through the YAML configuration file.
- The `Forward` Action has been reworked.
- The variable name containing the incoming data must now be defined under the key `data`, whereas the actions for processing incoming data are defined under the key `on_result`.
- The top-level key `messages` must be included for any outputs that reject or accept assignments. These messages are added to the assignments so that the workers can know why their work was accepted or rejected.
- The `VerifyPolygon` Action now uses the top-level key `data` to define the variable that contains the polygons to be verified.
- The `Verify` Action has been dropped. The same functionality can be found in the `Forward` Action.

Adds a `no_exit` flag (boolean) to the `Pipeline` object. If set to `True`, the program won't exit after completing the pipeline.

This release adds a new Action named `VerifyPolygon`, which validates the bounding boxes created by crowdsourced workers.

The polygons are validated using Shapely, which is now required by the tool.

For an example of using this Action, see `examples/verify_demo.py`.

This release removes support for the manual configuration of CAPTCHAs on Toloka, which will be deprecated in the future. For a description of the new system, see this article: https://toloka.ai/blog/new-captcha/

This release adds support for golden tasks.

A demo can be found under `examples/gold_demo.py`.

Essentially, golden tasks are defined in the YAML configuration under the key `data/gold`, which should contain key/value pairs for *output* columns and the columns that contain the golden answers in the TSV file.

To exemplify, if you have golden answers for the output named `result`, which are stored in a column with the header `gold` in the TSV file, the key/value pair `result: gold`.