Implement a skeleton of the Superfish interstitial

components/certificate_reporting/cert_logger.proto

Index: components/certificate_reporting/cert_logger.proto
diff --git a/components/certificate_reporting/cert_logger.proto b/components/certificate_reporting/cert_logger.proto
index 811d918a323c53f897060e02199934440d9534b6..0d4b7601ca1d0c76b3aa146c99ddba632e2373eb 100644
--- a/components/certificate_reporting/cert_logger.proto
+++ b/components/certificate_reporting/cert_logger.proto
@@ -28,12 +28,15 @@ message CertLoggerInterstitialInfo {
   // a user.
   enum InterstitialReason {
     UNKNOWN_INTERSTITIAL_REASON = 0;
-    // A standard SSL interstitial
+    // A standard SSL interstitial.
     INTERSTITIAL_SSL = 1;
-    // An interstitial alerting the user that they are in a captive portal
+    // An interstitial alerting the user that they are in a captive portal.
     INTERSTITIAL_CAPTIVE_PORTAL = 2;
-    // An interstitial telling the user to update their system clock
+    // An interstitial telling the user to update their system clock.
     INTERSTITIAL_CLOCK = 3;
+    // An interstitial telling the user to remove the Superfish software from
+    // their system.
+    INTERSTITIAL_SUPERFISH = 4;

[meacer, 2017/06/22 22:35:37]

This is no longer needed, right? Or if we want to keep track of it, we can still
set it, but not sure if there is value in doing so.

[estark, 2017/06/22 23:17:48]

I was no longer setting this properly, I fixed that (this also needs a test,
which I'm deferring bc time crunch: crbug.com/735803). But I think it's useful
to have. We won't have e.g. Finch info for this interstitial in cert reports, so
it'll be useful to know definitely which cases we showed the Superfish
interstitial in.

[meacer, 2017/06/22 23:22:02]

SG.

   }
 
   // The type of interstitial that was shown