Consider caching SAST artifacts in comparison endpoint

The following discussion from !15114 (merged) should be addressed:

  • @stanhu started a discussion: (+1 comment)

    This step looks like it will retrieve a report from object storage on GitLab.com (or local disk). Do we plan on caching/storing the diff somewhere so that we don't have to recalculate each time the endpoint is hit?

Assignee Loading
Time tracking Loading