Feature - After Issue Metadata Sync happens, there should be a full metadata sync report in JSON, Markdown and PDF

[joshua-quek-sonarsource]

• After Issue Metadata Sync happens, there should be a full metadata sync report in JSON, Markdown and PDF.
• The intent of this is so that the end user can see the deltas on which issue metadata got synced and which did not.
• Reasons of not metadata not syncing properly could be due to:
  • maybe the rule in the target (i.e. sonarcloud) does not exist
  • or it could be that the rule was not inside the quality profile attached to that project in sonarcloud
  • connection error or timeout which caused it to be skipped
  • ...maybe think of more edge cases on why an issue metadata does not sync?
  • or "unknown" if it is a bug that causes it to silently fail syncing for that issue

By the end of this, for the transfer of an individual project, a migrate of a full sonarqube instance, then there should be a few metadata sync reports - JSON, Markdown an PDF

These reports have to be exhaustively detailed but also extremely neatly structured, so that the end user knows where the gaps are and why certain issues are different or did not get fully synced.

[joshua-quek-sonarsource]

++ @okorach-sonar