As Hyper touched on, the problem is that Google's server is not configured with
CORS (cross-origin resource sharing). That makes it impossible for an external JavaScript application to load that particular url directly. This isn't a problem when CORS is enabled on a server (such as GitHub pages) or you control the servers yourself (in which you can enable cors). If you were to copy KML_Samples.kml to the same server Cesium was running, it would work as well. That link above should fill in any details for you.
If you absolutely have to load uncontrolled remote data, the solution is to use a proxy. Cesium ships with a development server that contains a local proxy that will retrieve anything for you, but for production applications you will need to set up something on your own server. So if you run Cesium locally with the supplied server, the below will work:
var viewer = new Cesium.Viewer('cesiumContainer');
var promise = Cesium.KmlDataSource.load(url,{
proxy : new Cesium.DefaultProxy('/proxy/')
});
viewer.dataSources.add(promise);
Note, this code will not run on the public
cesiumjs.org server because we do not run an open proxy (which is generally a bad idea), you need to be running the local node server that ships with Cesium.