* Also put Play Store fields under version control.
* Fix build errors.

This will make long checklists on marginally faster. So solve the issue properly we'll have to switch to a `RecyclerView`.

This is an initial redesign and refactoring of the light theme. This also prepares for a future dark theme.
The new theme was separated into a new module so we can share it among modules.

fix android.util.AndroidRuntimeException: Calling startActivity() from outside of an Activity  context requires the FLAG_ACTIVITY_NEW_TASK flag. Is this really what you want? (#947)

This adds a few more RowData implementations to support the implementation of SubTasks.

When a child task refers to its parent via the parents UID and the parent is inserted after the child, we need to update the PARENT_ID of the child once the parent is available.

PARENT_ID was meant to serve as a shortcut to parent-child relationships between tasks, for both writing and reading.
While the reading part already works (with the exception of issue #877) the writing part didn't work yet. This is fixed by this commit.

Also show task in widget in red color also if due date is equal to now. Otherwise a task would wrongly remain white if its view is updated exactly at the due date.

Use an important notification to inform the user about a stale list rather than launching an activity from the background.

In addition this changes the check list UI. Instead of splitting the description into
a description and check list part, we treat each paragraph either as text paragraph or check list item. Checkable items and text items can be converted into each other.

Translation correction.

Try to work around the crash caused by an IllegalStateException by always returning a valid group view. Some change in Android seems to cause this. We'll keep this workaround until we've removed the `ExpandableListView`for good.

Update Polish translation.

Translation update.

In order to support simple recurrence models and also keep long running tasks small we detach completed instances at the beginning of a series into separate task instances.

Also update gradle wrapper and travis file and fixes a build error.

The total number of users of Android versions < 4.4 sums up to less than 1% on Google Play. That's not enough to justify supporting these legacy versions anymore. Dropping these, on the other hand, allows us to ignore backwarnds compatibility issues.

Added Danish translation.

The Task Editor used to launch the details view for newly created tasks using the task Uri. In general this works, but it fails when the details view uses the Uri with the notification service (because that currently requires an instance Uri). So to fix this we load the first instance after creating a new task and use that one to show the details view.

Under certain conditions the CursorTreeAdapter might have had a null Cursor. This commit attempts to fix this by passing an empty MatrixCursor instead. Hopefully this fixes #758 until we got rid of the CursorTreeAdapter.

`DueData` and `TimeData` should not set recurrence values. That's not allowed on the instances table and, apparently, it's very unexpected and error prone.

This commit (temporarily) allows tasks with floating start or due and absolute until part in the RRULE and vice versa.
Apparently such tasks exist and we didn't validate this condition. So for now we tolerate this issue until we can be sure
the database won't contain such tasks.

Apparently there are tasks which have a recurrence rule but neither a dtstart nor a due date. This caused an NPE. By treating such tasks as non-recurring this should be fixed.

Recurring tasks may specify a dtstart and due date (instead of a duration). If the task was an all-day task, we may have tried to add a duration derived from the difference between start and due.
The result was a non-all-day duration (although in most cases being a multiple of 24h) and adding this to an all-day date resulted in an error. It's fixed by converting the duration into a proper
all-day duration.

Updates TaskProvider to skip updates which don't change any value. In such case no database operation is necessary and no notifications will be triggered.

Upon moving a task to a new list, it's not just moved, but a deleted copy is left behind in the old list, so sync adapters can take note of the removal in the old list.
This commit fixes the creation of the deleted instance. The code tried to create instance columns in the task table, which failed and caused the deleted instance to be missing.

This commit ensures that the TaskAdapter which is used to insert the deleted instance does not contain instance values.

It's no longer necessary to update all values which affect recurrence in the same update. The provider can handle updates of individual fields.

This commit adds initial recurrence support in that recurring instances are handled correctly when instances are edited or deleted.
In order to support this, the UI now operates on the Instances table rather then the tasks table. The instances table now supports deletes, and updates like the tasks table with the difference that all these operations only affect the specific instance that's addressed. All the operations on the instances table are converted into operations on a task by creating exception instances and RDATEs or EXDATEs.

Inserting instances is currently not possible because only a fixed number of instances are expanded. This means an instance inserted beyond the expansion window would still not show up in the instances table.
See https://github.com/dmfs/opentasks/issues/741

There is still room for improvement in that we could split of completed tasks and modify recurrence rules when deleting instances from the start or end of the series. That's left to future updates.
Also there is no UI yet to create or edit recurrence properties itself.

At present there is only one upcoming instance expanded, so you can only see the "current" instance (and all completed ones). This may/will change in future but may require some UI changes as well.

In order to support this commit a number of tests have been implemented which test creating and altering recurring instances.

Currently an exception is created when a recurring instance is modified which wasn't an exception before. This approach is RFC 5545 compliant but not supported by Apple clients. This will be fixed in future updates.