Making ChromeDriver directly implement the interfaces representing features it implements.

Currently, LocationContext and WebStorage are the only capabilities chromedriver returns, regardless of the kind of Chrome browser it is driving.

Augmentation never worked well on ChromeDriver, e.g. issue 6681 , and at times has been completely broken.

Because default ChromeDriver constructor starts a new session it cannot be augmented without consequences. A workaround has not been found.

Overriding getScreenshotAs() is dropped as redundant, RemoteWebDriver implementation works identically.

Signed-off-by: Jason Leyba <jmleyba@gmail.com>