1002946: Fix entitlement dates not being updated when pool dates change.

Caused issues where sub-pool dates looked correct, but consumer status
was inaccurate because calculation was done using entitlement dates
rather than the pool.

No need for duplication of this data, so drop the entitlement date
columns and use the pool instead.

Entitlement will still report a start/end date to maintain API
compatability, it just comes from the pool now.
1004780: truncate result string to fit in db

The JobStatus.update() method was not calling the setResult method, which
means the result would be set to whatever string the JobExecutionContext
had, even one longer than 255 characters. This issue was fixed some time
ago in the setResult() method, where we truncate the text.

The JobStatus.update() method was changed to call setResult() to avoid
this data issue. While there, update() now calls setState() as well.
The other members do not have setters or data transformations, so no
setters were called for those.

Added a test in the JobCuratorTest because this error only surfaced when
using an actual database.
Merge pull request #370 from candlepin/bz1004780

1004780: truncate result string to fit in db
Merge pull request #369 from candlepin/dgoodwin/drop-ent-dates

1002946: Fix entitlement dates not being updated when pool dates change.
Automatic commit of package [candlepin] release [0.8.26-1].
Fix deleted consumer spec to run in parallel.
Refactor import/export methods into a class.