ci: ignore CVE-2024-0567 and CVE-2023-5981 to fix ci

[salaxander]

Describe the changes in this pull request using active verbs such as Add, Remove, Replace ...

Closes #<issue_ID>

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (2602d59) 32.51% compared to head (01b930a) 34.18%.
Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #506      +/-   ##
==========================================
+ Coverage   32.51%   34.18%   +1.67%     
==========================================
  Files          17       17              
  Lines        1621     1293     -328     
==========================================
- Hits          527      442      -85     
+ Misses       1062      819     -243     
  Partials       32       32              

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

[salaxander]

@sozercan would we still expect the CI to be failing with this PR?

[sozercan]

@salaxander sounds like issues have not been addressed. you can test individually or add them back in

[sozercan]

reverting last commit to unblock #508

[salaxander]

Still seeing failures :(. The tests orginally failed before I had cleared those other 2 CVEs too

[ashnamehrotra]

the trivy command and file looks correct in the test logs, https://github.com/ashnamehrotra/copacetic/actions/runs/7938093411/job/21676447774#step:9:101 but copa is still checking for the error https://github.com/ashnamehrotra/copacetic/actions/runs/7938093411/job/21676447774#step:9:1897. Maybe it could be something within trivy?

[sozercan]

looks like CVE-2023-5981 is also marked as needing u5 so ignoring that too, this should fix it i think

[sozercan]

@ashnamehrotra fyi - it was hard to test since it was just locking without your pr without giving the error, i merged them both in #509 to test