ci: update CI dependencies and improve Snyk error handling

[Pymetheus]

Description

Make CI resilient to Snyk code test failures by adding continue-on-error: true to the Snyk step so the workflow won't fail on Snyk issues. Also update the Bandit invocation to load configuration from pyproject.toml (-c pyproject.toml) when generating the JSON report.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Code refactoring
• Performance improvement
• Test addition or update

Related Issue

Synk failed on issue, without generating a report to review the issue

Changes Made

• adding continue-on-error: true to the Snyk step so the workflow won't fail on Snyk issues
• update the Bandit invocation to load configuration from pyproject.toml (-c pyproject.toml)

Testing

Describe how you tested your changes:

• Unit tests pass
• Integration tests pass
• Manual testing performed

Screenshots (if applicable)

Add screenshots to help explain your changes.

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have updated the documentation accordingly
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Additional Context

Add any other context about the PR here.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!