Add kythe support to plugins and format the spec files

pkg/analyzer_plugin/tool/spec/common_types_spec.html

Index: pkg/analyzer_plugin/tool/spec/common_types_spec.html
diff --git a/pkg/analyzer_plugin/tool/spec/common_types_spec.html b/pkg/analyzer_plugin/tool/spec/common_types_spec.html
index ea938c88ea50275be0dd41a5788d232ea9111742..831d0795863300b4695c58fb6977bb0e1890eb33 100644
--- a/pkg/analyzer_plugin/tool/spec/common_types_spec.html
+++ b/pkg/analyzer_plugin/tool/spec/common_types_spec.html
@@ -808,6 +808,95 @@
       </value>
     </enum>
   </type>
+  <type name="KytheEntry">
+    <p>
+      This object matches the format and documentation of the Entry object
+      documented in the
+      <a href="https://kythe.io/docs/kythe-storage.html#_entry">Kythe Storage
+        Model</a>.
+    </p>
+    <object>
+      <field name="source">
+        <ref>KytheVName</ref>
+        <p>
+          The ticket of the source node (must not be empty).
+        </p>
+      </field>
+      <field name="kind">
+        <ref>String</ref>
+        <p>
+          An edge label (may be empty). The schema defines which labels are
+          meaningful.
+        </p>
+      </field>
+      <field name="target">
+        <ref>KytheVName</ref>
+        <p>
+          The ticket of the target node (may be empty).
+        </p>
+      </field>
+      <field name="fact">
+        <ref>String</ref>
+        <p>
+          A fact label (must not be empty). The schema defines which fact labels
+          are meaningful.
+        </p>
+      </field>
+      <field name="value">
+        <list>
+          <ref>int</ref>
+        </list>
+        <p>
+          The <tt>String</tt> value of the fact (may be empty).
+        </p>
+      </field>
+    </object>
+  </type>
+  <type name="KytheVName">
+    <p>
+      This object matches the format and documentation of the Vector-Name object
+      documented in the
+      <a href="https://kythe.io/docs/kythe-storage.html#_a_id_termvname_a_vector_name_strong_vname_strong">Kythe
+        Storage Model</a>.
+    </p>
+    <object>
+      <field name="signature">
+        <ref>String</ref>
+        <p>
+          An opaque signature generated by the analyzer.
+        </p>
+      </field>
+      <field name="corpus">
+        <ref>String</ref>
+        <p>
+          The corpus of source code this <tt>KytheVName</tt> belongs to.
+          Loosely, a corpus is a collection of related files, such as the
+          contents of a given source repository.
+        </p>
+      </field>
+      <field name="root">
+        <ref>String</ref>
+        <p>
+          A corpus-specific root label, typically a directory path or project
+          identifier, denoting a distinct subset of the corpus. This may also be
+          used to designate virtual collections like generated files.
+        </p>
+      </field>
+      <field name="path">
+        <ref>String</ref>
+        <p>
+          A path-structured label describing the “location” of the named object
+          relative to the corpus and the root.
+        </p>
+      </field>
+      <field name="language">
+        <ref>String</ref>
+        <p>
+          The language this name belongs to.
+        </p>
+      </field>
+    </object>
+  </type>
   <type name="LinkedEditGroup">
     <p>
       A collection of positions that should be linked (edited simultaneously)