ci(client-python): adding bandit as a sats quickwin (#355)

[Ferdinand (guzmud)]

Proposed changes

• Adding non-blocking step that runs bandit on the code

Testing Instructions

1. Step-by-step how to test
2. Environment or config notes

Related issues

• Closes ci(client-python): adding PyCQA/bandit step to the CI for improved code quality/security (SATS quickwin) #355

Checklist

• I consider the submitted work as finished
• I tested the code for its functionality
• I wrote test cases for the relevant uses case
• I added/update the relevant documentation (either on github or on notion)
• Where necessary I refactored code to improve the overall quality
• For bug fix -> I implemented a test that covers the bug

Further comments

[Copilot]

🟡 Changes recommended

The scan cannot locate Bandit and is blocking despite being described as non-blocking.

2 open findings

• Bandit is unavailable because the virtual environment is not activated · New
• Bandit findings fail the job despite the scan being non-blocking · New

What changed in this PR

Adds Bandit security analysis to CI for the Python client.

Changes:

• Runs Bandit against application, script, and test code.
• Triggers analysis for pull requests and pushes to main.

File	Description
.github/​workflows/​sats-analysis.yml	Defines the Bandit analysis workflow.

🧠 Review effort: Balanced

---

Give feedback about Copilot approvals in this survey to enter a drawing for a $150 gift card.