Renaming Supertask, Pretask and TaskWrapper

[zyronix]

Currently there is a lot of confusion for the naming of the Supertask, Pretask and TaskWrapper. So the currently description and why the exists:

Supertask

Basically the SuperTask exists to create somekind of template for groups of common tasks that you want to apply to an hashlist. EG: my standard list of attack for cracking WPA2 hashes.

Pretask

Pre configure task of repeating use cases. EG: Single attack with rockyou and best64. Pretask can be part of a Supertask.

TaskWrapper

Once a SuperTask is applied to an Hashlist, it will become a TaskWrapper in the database with the TaskType set to 'supertask'. The pretask attach to the supertask will become Task objects in the database. Basically, this is a running supertask.

However, if you apply a Pretask directly to an Hashlist (thus just create a normal task) another TaskWrapper is also created. But this time it will set the TaskType value in the database to 'task'. And only one Task object will be linked to TaskWrapper.

Because those naming are a bit confusion, because at somepoint when you interact with task via the API or UI, it will inform you that a TaskWrapper of TaskType supertask is a Supertask; but it not, it is a TaskWrapper. Supertasks are in essense only the templates.

[zyronix]

Related to #991