docs: Explain how to report a security issue.

[MaxJPRey]

Description

As title says.
This will be used for all the other repos of our organization.

Issue linked

Please mention the issue number or describe the problem this pull request addresses.

Checklist

• I have tested my changes locally.
• I have added necessary documentation or updated existing documentation.
• I have followed the coding style guidelines of this project.
• I have added appropriate unit tests.
• I have reviewed my changes before submitting this pull request.
• I have linked the issue or issues that are solved to the PR if any.
• I have assigned this PR to myself.
• I have added the minimum version decorator to any new backend method implemented.
• I have made sure that the title of my PR follows Conventional commits style (e.g. feat: extrude circle to cylinder)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.28%. Comparing base (cc31b93) to head (7e8510b).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1605   +/-   ##
=======================================
  Coverage   91.28%   91.28%           
=======================================
  Files          86       86           
  Lines        7103     7103           
=======================================
  Hits         6484     6484           
  Misses        619      619           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[RobPasMue]

Why not use GH's admonition system? Looks much better that way... See for ref: https://blog.solichain.com/how-to-create-admonitions-in-github-markdown-ab580debcfdc