trivy repo level scan for python agent

[daniellim1]

Before contributing, please read our contributing guidelines and code of conduct.

Overview

Describe the changes present in the pull request

Related Github Issue

Include a link to the related GitHub issue, if applicable

Testing

The agent includes a suite of tests which should be used to
verify your changes don't break existing functionality. These tests will run with
Github Actions when a pull request is made. More details on running the tests locally can be found in our
testing guidelines,
For most contributions it is strongly recommended to add additional tests which
exercise your changes.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.55%. Comparing base (312a322) to head (780e959).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1519      +/-   ##
==========================================
- Coverage   81.59%   81.55%   -0.04%     
==========================================
  Files         206      206              
  Lines       23689    23689              
  Branches     3753     3753              
==========================================
- Hits        19328    19320       -8     
- Misses       3100     3104       +4     
- Partials     1261     1265       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ daniellim1
❌ mergify[bot]
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[hmstepanek]

We don't change this image very often and it's only used for testing so maybe we could move this scanning into our build ci image workflow so it only scans when a new image is built? This happens inside our .github/workflows/build-ci-image.yml where it can be triggered by a cron schedule or manually.