Newlines in SARIF parser code blocks

[ahmsec]

Description

Bug: The SARIF parser doesn't add a newline after the triple backticks for Markdown code blocks. This breaks code blocks on platforms like Jira, since that line is used for language identifiers. See for example https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks#syntax-highlighting.

Fix: This PR simply adds newlines to the Markdown code block delimiters.

Test results
./dc-unittest.sh --profile postgres-redis --test-case unittests.tools.test_sarif_parser.TestSarifParser passes

Documentation

Checklist

This checklist is for your information.

• Make sure to rebase your PR against the very latest dev.
• Features/Changes should be submitted against the dev.
• Bugfixes should be submitted against the bugfix branch.
• Give a meaningful name to your PR, as it may end up being used in the release notes.
• Your code is flake8 compliant.
• Your code is python 3.11 compliant.
• If this is a new feature and not a bug fix, you've included the proper documentation in the docs at https://github.com/DefectDojo/django-DefectDojo/tree/dev/docs as part of this PR.
• Model changes must include the necessary migrations in the dojo/db_migrations folder.
• Add applicable tests to the unit tests.
• Add the proper label to categorize your PR.

[dryrunsecurity]

Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.

DryRun Security	Status	Findings
Configured Codepaths Analyzer	✅	0 findings
Sensitive Files Analyzer	✅	0 findings
AppSec Analyzer	✅	0 findings
Authn/Authz Analyzer	✅	0 findings
Secrets Analyzer	✅	0 findings

Note

🟢 Risk threshold not exceeded.

Powered by DryRun Security

[Maffooch]

Looks like the unit tests need to be updated as well

[ahmsec]

@Maffooch Whoops, I updated the unit tests. Could you approve rerunning the workflow?

[mtesauro]

@ahmsec Tests have been re-kicked

[mtesauro]

Approved

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[mtesauro]

@ahmsec This can be merged once the merge conflict is resolved.

[github-actions]

Conflicts have been resolved. A maintainer will review the pull request shortly.