[JanGunar]

What GitHub issue does this PR apply to?

Resolves #795

What changed and why?

Added GitHub Actions workflows for OSV Scanner.

The changes include:

• Running OSV Scanner on pull requests.
• Running OSV Scanner on a weekly schedule.
• Using the official OSV Scanner GitHub Action.

These workflows help detect vulnerable or outdated dependencies automatically.

AI bots used in the process of making this PR

GitHub Copilot was used to help write the final pull request description.

Checklist

• I claimed any associated issue(s) and they are not someone else's
• I have looked at documentation to ensure I made any revisions correctly
• I tested my changes locally to ensure they work correctly
• For language files, I have validated the edited files are valid JSON and data shows up correctly
• For website code edits, I have added or edited any appropriate unit tests for my changes
• If I used artificial intelligence (AI), I have reviewed the suggested changes and ensured they work correctly

Any additional comments or things to be aware of while reviewing?

The workflows will also be checked by GitHub Actions after this pull request is opened.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.