Request for parallel primary tasks

[sekgobela-kevin]

This issue is part of enhancement to loop some producer which would allow producer to execute multiple primary items records.
This could mean that at a time for example, multiple usernames are being tried instead of waiting for one to complete before
advancing to the next username.

That may improve speed of attack in some cases espacilly if table used is too powerful or specific to target being targeted.
Target will be shocked to findout that multiple primary items(e.g usernames) are being tried.

[sekgobela-kevin]

This issue can be considered as resolved as source files for have been written.
In the past few days I have been working very hard on allowing parallel primary tasks.
It works well and both unit and integrated tests are doing well with it added.

[sekgobela-kevin]

This issue can be easily resolved by manipulating producer.
This issue only applied to loop some producer and primary column is required.

[sekgobela-kevin]

Resolving this issue may raise another issue which is inconsistent results which would cause tests to fail.
This can be caused by iterators as its not possible to read same value multiple times as iterators get exausted.
That can be avoided by using product.itertools() instead of using product.Product.product_callable() created from this project`

Luckily product.product() also calls itertools.product() if neccessay. Its just a matter of allowing users of project to enable or
disable use of using callables product(product.Product.product_callable()).

Commit which resolves this issue does something to avoid problem in this comment.
Thankfully the issue was detected by integrated tests when using FieldFile object which depends on file object.