(e2e)Ensure Rapidast logs a valid ZAP SARIF file

[cedricbu]

SARIF JSON schema downloaded from:
https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/schemas/sarif-schema-2.1.0.json

[cedricbu]

Quick additional notes:

• This is probably the first of several PRs: if the PR is accepted, ideally, the same test will be added in other compatible scanners
• I actually didn't manage to find an easy way to run the full patched e2e code locally, so there may be issues with the code itself (typos, etc.)
• Currently, the ZAP e2e sanity test is done against the ZAP native report. I would probably make sense to remove that native report and make those sanity tests against the SARIF one

[sfowl]

I actually didn't manage to find an easy way to run the full patched e2e code locally, so there may be issues with the code itself (typos, etc.)

This seems to have run and pass so looks like it's issue free! We should have better docs on this though, that's probably on me for not yet writing something like an e2e-tests/README.md.

Currently, the ZAP e2e sanity test is done against the ZAP native report. I would probably make sense to remove that native report and make those sanity tests against the SARIF one

Against the custom SARIF report made by rapidast? I agree there's probably more value in testing that one. If it's cheap to run, is it worth testing both?