[clippy] Add all help messages to tricium comments

In addition to the main message of a lint, also add all the child help
messages to each Clippy Tricium comment. This will provide additional
information to CL authors (often including suggestions for fixing the
lint) and also automatically handles linking to the documentation for
the lint, as a link to the docs is often included in the help messages.

This also causes Tricium to stop adding broken links for undocumented
warnings like `unused_variables`, as we no longer assume that every lint
has a corresponding documentation URL and instead only add a URL if
Clippy thinks it exists.

Also, slightly simplify the test utility code for writing fake Clippy
results to a JSON-lines file.

Change-Id: If5e4cbde98fec6bb696609ad6e9e0bb451f388d0
Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/645461
Fuchsia-Auto-Submit: Oliver Newman <olivernewman@google.com>
Reviewed-by: Joseph Ryan <josephry@google.com>
Commit-Queue: Joseph Ryan <josephry@google.com>
2 files changed
tree: fd84f486167224dc18c672c680536574ee0e68d9
  1. boards/
  2. build/
  3. bundles/
  4. docs/
  5. examples/
  6. garnet/
  7. products/
  8. scripts/
  9. sdk/
  10. src/
  11. third_party/
  12. tools/
  13. zircon/
  14. .clang-format
  15. .clang-tidy
  16. .git-blame-ignore-revs
  17. .gitattributes
  18. .gitignore
  19. .gn
  20. .style.yapf
  21. analysis_options.yaml
  22. AUTHORS
  23. BUILD.gn
  24. CODE_OF_CONDUCT.md
  25. CONTRIBUTING.md
  26. LICENSE
  27. OWNERS
  28. PATENTS
  29. pyrightconfig.json
  30. README.md
  31. rustfmt.toml
README.md

Fuchsia

What is Fuchsia?

Fuchsia is an open source, general purpose operating system supporting modern 64-bit Intel and ARM processors.

We expect everyone interacting with our project to respect our code of conduct.

Read more about Fuchsia's principles.

How can I build and run Fuchsia?

See Getting Started.

Where can I learn more about Fuchsia?

See fuchsia.dev.