(TWILL-105) Remove ZKDecoratorService and some pom file fixes

- The ZKDecoratorSerivce is complicates and is not necessarily and have complicated race condition inside
- Most of the functionalities in ZKDecoratorService are moved into AbstractTwillService
  - It uses AbstractExecutionThreadService from guava that simplifies a lot of service+zk related interactions
  - Remove use of StateNode and updating of Service states in ZK as no one is actually using it
- The Hadoop secure store related code in AbstractTwillService are moved into AbstractYarnTwillService
- Fixes in the pom.xml
  - There should be one Hadoop version profile that is activeByDefault
  - Increase memory size for unit-test
- Fix YARN test cases
  - Correct assertion in ResourceReportTestRun.testResourceReportWithFailingContainers
This service/runnable still function. However, data carries inside liverNode won't be available. Also, the controller will resort to polling (in Yarn twill controller case, polling RM. In AM case, currently it doesn't use the live node) for the service states. I don't have a definite answer on whether we should stop the service or not. I am open for discussion.

Also, all ZKClient used in Twill are FailureRetryZKClient, hence for interim errors (e.g. connection-loss, session-time), it automatrically retries already, hence not causing create node call fails.