Asset CDN: Not all core/jetpack files are served from CDN

#### What I expected

Here is list of files which is served from my test site with Asset CDN enabled. I think we can serve them from our CDN.

- wp-admin/css/colors/sunrise/colors.min.css?ver=4.9.8
- wp-includes/js/wp-emoji-release.min.js?ver=4.9.8

The below addresses were included in the original report and deemed wontfix or invalid:

- ~wp-admin/admin-ajax.php?action=atd_settings&ver=20150715~
- ~Not sure about this one: https://fonts.googleapis.com/css?family=Noto+Serif:400,400i,700,700i&subset=cyrillic,cyrillic-ext,greek,greek-ext,latin-ext,vietnamese~
- ~WPCOM themes: wp-content/themes/nikau-wpcom/style.css?ver=20160507~

Start by tracing Jetpack's Asset CDN handling for wp-admin/css/colors/sunrise/colors.min.css and wp-includes/js/wp-emoji-release.min.js, then check how these paths are classified and routed. Done means both listed assets are served through the CDN when Asset CDN is enabled, with appropriate tests covering the routing.

Written by the indexing model from the issue text.