Instead of two methods we now have one that does the appropriate
action based on the input type.

SETRA has a default value for this field, making it optional.

Setra expects datetime.datetime, not datetime.date
In addition, voucherdate is in fact not optional.

- Both get_batch_errors and get_batch_complete now return objects
  unless the client parameter return_objects is set to False
- Tests for models, endpoints and client methods are included.

Validation rule 12 on Batches in SETRA sets the default value before
transfer to Unit4ERP(UBW) if it is not set. The attribute is thus not
required.

There are validation rules in SETRA that sets this value to a default
value set in the parameters table of SETRA. For this to be possible
we must allow users to leave out the value.

Also updated and fixed tests, fixtures and readme

And added two new tests

This gives us more options for how to use the function, and makes setra client easier to use in Bookitlab-api (BOOK-17)

batchid- and voucherno_interface are not used.

They where originally added because someone thought we should enforce
relations in software 

This allows us to catch more errors that can occour when transferring
data to Setra.

Introduces SetraClient. The client is made
for use against the SETRA(SEntralt TRAnsaksjonslager) API.

There are models for Batch, Voucher, Transaction and Multi, where Multi is
a combination of the preceding, The Multi model validates that the batchid
of the voucher matches the batch included, and that the voucherid of the
transactions matches one of the included vouchers.

Tests have also been included for the client itself, the endpoints, and
the models.

Configuration for tox, Jenkins and gitlab-ci are included for running
tests and building the client.