During the a PR /publish workflow, in addition to the workflow PR comments about published OCI images, failed plugin exports, we now also add backstage incompatibility report to the PR publish comment.

However, the Backstage incompatibility report is added as the first element in the PR comment, and with very big Markdown titles, so that it sort-of hides the rest of the comment with the list of well-published OCI images.
We should:

• Add the compatibility report as the last part of the PR comment
• Cleanup the markdown in order to have the report smaller and not hide the rest of the PR comment 
• Not mention "Publish failure" if only the backstage compatibility fails