Add proto for TLS error assistant, refactor proto generator code.

chrome/browser/resources/ssl/tls_error_assistant/tls_error_assistant.asciipb

Index: chrome/browser/resources/ssl/tls_error_assistant/tls_error_assistant.asciipb
diff --git a/chrome/browser/resources/ssl/tls_error_assistant/tls_error_assistant.asciipb b/chrome/browser/resources/ssl/tls_error_assistant/tls_error_assistant.asciipb
new file mode 100644
index 0000000000000000000000000000000000000000..2ec829a454d42c038648aa8c0838098fd66e013c
--- /dev/null
+++ b/chrome/browser/resources/ssl/tls_error_assistant/tls_error_assistant.asciipb
@@ -0,0 +1,13 @@
+# Copyright 2016 The Chromium Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+# Placeholder for list of known certificates that are treated as captive
+# portal certificates.
+
+# TODO(crbug.com/640835): Populate this with full list.
+version_id: 1
+
+captive_portal_cert {
+  sha256_hash: "testcert"

[Nathan Parker, 2016/12/10 00:56:50]

Are these binary strings, or hex?  Do you want them in sorted order?  Maybe
not... maybe you could just check in the python that there are no duplicates,
and that all are 32 bytes.  Expect typos here... :-)

Maybe each hash should have some # comments as to what it is and why it was
added? Something to think about.  You could add instructions here, or in a .md
file like I did.

[meacer, 2016/12/13 02:30:16]

Added some comments to describe the format. I'm planning to add the readme once
I have better validation code and the component lands. Does that sgty?

+}