don't support CoreAnimation

Reviewed by Darin Adler and Adam Roben.

WKCACFLayerRenderer::acceleratedCompositingAvailable() now creates 
a dummy HWND so that it can step through the whole setHostWindow() 
and createRenderer() process. createRenderer() also calls a new 
function, hardwareCapabilitiesIndicateCoreAnimationSupport() which 
can only be called  once we have a d3dDevice.

setHostWindow() and createRenderer() now both return bools that 
indicate whether or not they have succeeded.

* platform/graphics/win/WKCACFLayerRenderer.cpp:
(WebCore::hardwareCapabilitiesIndicateCoreAnimationSupport):
(WebCore::CoreAnimationTesterWindowWndProc):
(WebCore::WKCACFLayerRenderer::acceleratedCompositingAvailable):
(WebCore::WKCACFLayerRenderer::shared):
(WebCore::WKCACFLayerRenderer::createRenderer):
* platform/graphics/win/WKCACFLayerRenderer.h:
(WebCore::WKCACFLayerRenderer::setHostWindow):

WebKit/win: Tiny WebKit portion of fix for <rdar://problem/7485289> WebKit 
crashes on systems that don't support CoreAnimation

Reviewed by Darin Adler and Adam Roben.

setHostWindow() no longer calls createRenderer(), so now that has 
to be called manually.

* WebView.cpp:
(WebView::setAcceleratedCompositing):



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@55442 268f45cc-cd09-0410-ab3c-d52691b4dbfc