Display content settings for extensions with extension name.

chrome/browser/resources/settings/site_settings/zoom_levels.html

Index: chrome/browser/resources/settings/site_settings/zoom_levels.html
diff --git a/chrome/browser/resources/settings/site_settings/zoom_levels.html b/chrome/browser/resources/settings/site_settings/zoom_levels.html
index c94a13a5b897a80962d6d35445431aa9b2d0ae59..c00584f1f9cb42d76a803ee1841176aeb7fa4378 100644
--- a/chrome/browser/resources/settings/site_settings/zoom_levels.html
+++ b/chrome/browser/resources/settings/site_settings/zoom_levels.html
@@ -23,10 +23,10 @@
           rendered-item-count="{{renderedCount}}">
         <div class="list-item">
           <div class="favicon-image"
-              style$="[[computeSiteIcon(item.origin)]]">
+              style$="[[computeSiteIcon(item.originForFavicon)]]">
           </div>
           <div class="middle">
-            <div>[[item.origin]]</div>
+            <div>[[item.displayName]]</div>

[dschuyler, 2016/11/28 21:58:42]

WDYT: Would it help to filter zoom level sites 
through expandSiteException() and use originForDisplay
here? If a zoom level will never have an embedded origin
and will always have a displayName then maybe it won't help.

[dullweber, 2016/11/29 09:34:18]

I don't think the expansion code is useful because exceptions and zoomlevels
work differently.
Content-settings use scheme+host as origin and maybe an additional
embeddedOrigin to refer to a rule. Zoomlevels usually use just the host as an
identifier to have a consistent behavior between http and https urls. This is
the reason, why I have to use the weird extension detection code, to find out if
something is probably an extension and get the right extension url to find the
favicon.

           </div>
           <div>[[item.zoom]]</div>
           <div>