Fix for #111 (add possibility to specify queryset by filters)

[PetrDlouhy]

This is concept of possible fix for #111. It adds possibility to specify the queryset by filter parameters instead of just list of PKs.

Specifying export querysets by filters might be very beneficial in cases when the same export needs to run on regular basis (e.g. monthly) or executed multiple times with changed parameters.

Few issues to decide:

1. The export queryset in original django-import-export is specified by ModelAdmin filters, these are querset filters.
2. It would be nice if this export job could be created from the django-import-export workflow (for example by adding second button "Export with Celery job" beside "Submit" in the export view, but the difference from 1. complicates it.
3. It is also complicated, because django-import-export-celery uses ModelResource.get_export_queryset() which might have different annotations than ModelAdmin.get_queryset() and thus the same filters might not work.

I also converted the queryset field to JSONField because it has much better data validation, but I can take that change back or introduce in separate PR.