Enable securityReportFindings GraphQL to retrieve scanners

What does this MR do and why?

This MR fixes the PipelineVulnerabilitiesFinder to include the project_id in the scanner for the findings. This is necessary for the securityReportFindings GraphQL field to respond with the scanner data, as the `ScannerPolicy authorization is delegated to the project authorization.

Screenshots or screen recordings

Before

After

How to set up and validate locally

1. Check out the master branch
2. Make the following GraphQL call

query pipelineFindings {
  project(fullPath: "<project path>") {
    pipeline(iid:"<pipeline IID>") {
      securityReportFindings(first:1) {
        nodes {
          scanner {
            name
          }
        }
      }
    }
  }
}

3. The scanner should be null

{
  "data": {
    "project": {
      "pipeline": {
        "securityReportFindings": {
          "nodes": [
            {
              "scanner": null
            }
          ]
        }
      }
    }
  }
}

4. Check out this branch
5. Make the call again
6. The scanner should not be null

{
  "data": {
    "project": {
      "pipeline": {
        "securityReportFindings": {
          "nodes": [
            {
              "scanner": "<scanner name>"
            }
          ]
        }
      }
    }
  }
}

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #368601 (closed)