cargo deny create issue on schedule

[LesnyRumcajs]

Summary

Vulnerabilities in dependencies should not surface only during PR (although it's still beneficial, we rarely add new ones)—they should be reported regardless of whether any PR is made.

For dependencies checks, we use cargo deny, which unfortunately lacks the option to create issues on its own, unlike the archived https://github.com/actions-rs/audit-check?tab=readme-ov-file#scheduled-audit.

With https://github.com/JasonEtco/create-an-issue?tab=readme-ov-file, it's possible to use some templating to generate such an issue. The alternative could be using:

• using raw https://github.com/octokit/octokit.js
• contributing to the Create an issue when check fails EmbarkStudios/cargo-deny-action#64

Completion Criteria

• Create a workflow that periodically scans the repo for cargo deny check failures.
• The workflow should create an issue if the check fails. The issue should contain the following:
  • Title: what failed, e.g., RUSTSEC-2024-0436: paste - no longer maintained.
  • Content: what failed, e.g., output from the cargo deny check.
• The workflow should not recreate issues for the same dependency failure.

Additional Links & Resources