fix(sec): upgrade gitpython to 3.1.35

[Laihb1106205841]

What happened？

There are 1 security vulnerabilities found in gitpython 3.1.29

• CVE-2023-40267

What did I do？

Upgrade gitpython from 3.1.29 to 3.1.35 for vulnerability fix

What did you expect to happen？

Ideally, no insecure libs should be used.

How can we automate the detection of these types of issues?

By using the GitHub Actions configurations provided by murphysec, we can conduct automatic code security checks in our CI pipeline.

The specification of the pull request

PR Specification from OSCS