feat: implement sarif format reporter

[Zxilly]

Closes: #594

I asked earlier if anyone had already worked on this feature and got no reply #594 (comment) , so I added this implementation myself.

But as I declared, I'm not a professional rust developer, so this patch obviously contains a lot of problems caused by a lack of understanding of rust, such as .unwrap abuse, since I'm not sure how to properly convert Error to io::Error.

I enabled Allow edits by maintainers, so if you have any suggestions for syntax changes, please push them directly to the corresponding repository branch, thanks!

[Zxilly]

@epage Could you please approve the workflow run to see if anything broken by this?

[coveralls]

Pull Request Test Coverage Report for Build 9723606862

Details

• 0 of 76 (0.0%) changed or added relevant lines in 4 files are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.7%) to 22.315%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
crates/typos-cli/src/bin/typos-cli/args.rs	0	1	0.0%
crates/typos-cli/src/bin/typos-cli/main.rs	0	1	0.0%
crates/typos-cli/src/report.rs	0	2	0.0%
crates/typos-cli/src/bin/typos-cli/report.rs	0	72	0.0%

Files with Coverage Reduction	New Missed Lines	%
crates/typos-cli/src/bin/typos-cli/main.rs	2	0.0%

Totals
Change from base Build 9627078583:	-0.7%
Covered Lines:	534
Relevant Lines:	2393

---

💛 - Coveralls

[Zxilly]

@epage I have resolved the conflict.

[epage]

Sorry for the delays as I am slowly working through my backlog.

It would help if the commits were cleaned up to present this how you want it reviewed and merged.

It would also be good for us to have a test for this, likely among our end-to-end tests.

[Zxilly]

linter warning resolved

[Zxilly]

I suppose I could write some integration tests, but I'm not quite sure where the old tests are located, is there any architecture I could reuse?

[Zxilly]

I have added a test

[epage]

Sorry that I've fallen behind and not been able to get back to this yet.

I did want to quickly note that I just noticed the fix element
https://docs.oasis-open.org/sarif/sarif/v2.1.0/errata01/os/sarif-v2.1.0-errata01-os-complete.html#_Toc141791131

I wonder if github has integration for that so people get diffs in the post with the possibility of making a commit right from the review.

Note: I would not block merging this PR on getting that to work

[epage]

• Switched to code points
• Added more tests
• Improve handling of file name typos

[epage]

@Zxilly mind doing a pass over of my changes?

[Zxilly]

Look good to me, maybe we can add some cjk char to testcase?