Add validate-release workflow

[xschildw]

Problem:

• We used to run a Jenkins job to validate the python client against the staging repo and prevent releasing
  breaking changes. The Jenkins server has been sunset, I ran integration tests from my laptop but need
  a permanent solution.

Solution:

• I would like to create dispatch workflow in the SynapsePython client repo to run a single pass integration test.

Testing:

• None, I just trimmed an existing workflow. Considered testing in my fork but that means adding secrets etc., since
  this is a dispatch workflow it should have no effect on existing operations and can be debugged in the SageBio repo.

[Copilot]

Pull request overview

Adds a manually triggered GitHub Actions workflow intended to validate the Synapse Python client against a Synapse backend (replacing a retired Jenkins-based release validation path).

Changes:

• Add a new workflow_dispatch workflow to run unit tests and (optionally) integration tests when secrets are available.
• Bump the bandit pre-commit hook revision.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
.pre-commit-config.yaml	Updates the Bandit hook version used by pre-commit.
.github/workflows/validate-release.yml	Introduces a manual “validate release” workflow that installs dependencies, runs unit tests, and conditionally runs integration tests using decrypted config secrets.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[BryanFauble]

Some changes to make