✨ Optimize SAST check

[spencerschrock]

What kind of change does this PR introduce?

Optimization

• PR title follows the guidelines defined in our pull request documentation

What is the current behavior?

CheckRuns info is fetched via 30 REST API calls.

What is the new behavior (if this is a feature change)?**

Caches info about CheckRuns which is pulled in during the initial graphQL step without an increase in that API cost (currently cost=1). This makes the info available for the SAST check without needing 30 REST API calls.

If any uncached info is requested, REST API calls are performed, same as before.

• Tests for the changes have been added (for bug fixes/features)

Which issue(s) this PR fixes

Partial fix for #1916

Special notes for your reviewer

Might run into uncached scenarios for repos that don't squash on merge.

Does this PR introduce a user-facing change?

For user-facing changes, please add a concise, human-readable release note to
the release-note

(In particular, describe what changes users might need to make in their
application as a result of this pull request.)

NONE

[spencerschrock]

Need to double check E2E behavior on a repo that doesn't squash commits. When run on github.com/ossf/scorecard, everything is cached.

[codecov]

Codecov Report

Merging #2191 (3a126e4) into main (11ff78e) will decrease coverage by 0.35%.
The diff coverage is 2.66%.

@@            Coverage Diff             @@
##             main    #2191      +/-   ##
==========================================
- Coverage   42.28%   41.92%   -0.36%     
==========================================
  Files          95       95              
  Lines        7871     7935      +64     
==========================================
- Hits         3328     3327       -1     
- Misses       4283     4348      +65     
  Partials      260      260              

[azeemshaikh38]

Awesome work @spencerschrock with the quick turn around here! Can't wait to see this running in prod.

[spencerschrock]

Looks like some consistent failures in the e2e token tests. I'll take a look

[azeemshaikh38]

Looks like some consistent failures in the e2e token tests. I'll take a look

May need to include checks: read permission.

[github-actions]

Integration tests success for
[febb9ba]
(https://github.com/ossf/scorecard/actions/runs/2930013912)

[github-actions]

Integration tests success for
[a753fb2]
(https://github.com/ossf/scorecard/actions/runs/2930107336)

[github-actions]

Integration tests success for
[3a126e4]
(https://github.com/ossf/scorecard/actions/runs/2936194599)