Add tag to build locator and build details in TeamCity API
Add new V2 version of Continuous Deployment config
Add ability to track new tags

 - made teamcity tracking code more generic (using a build locator)
 - add logic for adding and removing trackers according to the continuous deployment configuration
Add trigger field to Continuous Deployment config list
Strip any $ from the classname when creating a logger

The presence of a $ (created for scala objects) seems to make it impossible to turn on debug, so we now strip it.
This has the side effect of singleton objects using the same logger as any class of the same name, but this is
 preferable.
Small formatting change for trigger text
Add some more features to the TeamCity API

 - The build summary fetcher can now follow continuation pages
 - Extra bits of information can be chained to a locator with sinceBuild and sinceDate instance methods
Add underlying functionality to trigger a deploy based on a tag

This adds the functionality for the TeamCity integration to detect newly tagged builds and also the
continuous deployment enhancement to register a listener for new tags and act on notifications when
they are delivered.

This is hard to achieve as the TeamCity API is less than amazing. Significant chunks of
code have been re-written in order to avoid repetition whilst keeping a reasonable level
of maintainability.
Make tag field disabled immediately (don't wait for JS to kick in)
Use stripSuffix to simplify this expression
Merge pull request #121 from guardian/sh-tagged-continuous-deployment

Continuous deployment enhancements