Changed should_try_to_verify_correct_number_of_times test to be independent on time problems

Fixed issue #66 (flaky test)
Flickering test - renamed DurationChecker to Timer, removed unnecessary interface (initially wanted to be in accord with convention but the interface was unnecessary), added test for timer, changed other tests to use the Timer.
Tidied up the code around the timeout verification.

Attempted to make the Timer class easier to comprehend.
Moved class to a better package.
"Update release notes by Travis CI build 255 [ci skip]"
Increment version '1.10.3' -> '1.10.4' by Travis CI build 255 [ci skip]
Regenerated the release notes [ci skip]
Improved the build logic related to releases.

Avoided the hack with applying the release-notes plugin late. Added task for updating release notes locally for dry-running purposes [ci skip]
Fixed the transient problem that caused test failures.

Ensure the state is reset correctly after a test run. Enabled back the test that was disabled previously.
Fixed #90 Mockito hints at the "non public parent" problem.

During state validation, when invalid use of the API is detected, Mockito also hints at the limitation of the mocking engine, that we don't support mocking methods that are declared on non-public parent class.
Added specific exception type.

Related to #90. It feels this scenario deserves a custom exception type.
Tidy up: renamed a test, added javadoc, removed @Ignored test
"Update release notes by Travis CI build 256 [ci skip]"
Increment version '1.10.4' -> '1.10.5' by Travis CI build 256 [ci skip]
Added a TODO [ci skip]
Updated the commit numbers for 1.10.0 [ci skip]
Fixed links in notes for older versions [ci skip]
C.D. machinery - simplified the retrieval of bintray github API

There is no point using a project property API, env. variables for local testing and development work just fine (we have to use env vars anyhow as Travis uses them).
C.D. machinery - exposed a method for incrementing versions

This way, we can increment versions without invoking the task. This is useful for building a release procedure.
C.D. machinery - reworked the release steps

Enhancement #95

1. Changed the user to be an artificial 'Continuous Delivery Drone' instead of myself.
2. Added some basic dry-running capabilities (needs more work and tidy-up).
3. Changed the procedure so that there is only one git push at the end.