[Spike] Evaluate effort for compliance with Jupiter Readiness checklist

Timebox: a day (Friday?) to get this done

https://docs.engineering.redhat.com/pages/viewpage.action?spaceKey=JUP&title=Jupiter+Source+files+readiness+Checklist

Review the Jupiter Readiness checklist and evaluate the effort required for Service Mesh, Jaeger, and distributed tracing docs to meet the requirements.

Also find out what happens if something doesn't comply?  (Does it break the build?  Not publish correctly?)

Check for:

Attributes files - Effort to combine with common-attributes.adoc

Assemblies - lines between includes

Content type tags on modules (Some of this will be automated)

Module heading levels

Modules that need to be broken up (contain multiple headers)

Abstracts - (Still need clarity on whether abstracts are published or purely metadata)

Spreadsheet where I'm tracking our topics against the checklist is here

https://docs.google.com/spreadsheets/d/1nGbJeLtcEarHZ4NWIzDzKhXWrH-12dKKJLloQP8Do0Y/edit#gid=936933957