freetype_ftfuzzer oss-fuzz benchmark uses outdated commit

[ndrewh]

the benchmark.yaml in master currently is quite misleading:

fuzzbench/benchmarks/freetype2_ftfuzzer/benchmark.yaml

Lines 15 to 18 in c734a74

	commit: cd02d359a6d0455e9d16b87bf9665961c4699538
	commit_date: 2023-01-28T16:04:38+00:00
	fuzz_target: ftfuzzer
	project: freetype2

That commit (cd02d359a6d0455e9d16b87bf9665961c4699538) is not from 2023, it is from 2017. Imagine my surprise when a long fuzzing run ended and I look through the coverage report and find out I'm looking at 6-year-old code!

As far as the freetype build issue referenced in #1688 goes, it looks like someone is not setting or using SANITIZER correctly. If you add export SANITIZER=none to the build.sh script that is copied in when you run:

python3 benchmarks/oss_fuzz_benchmark_integration.py -p freetype2 -f ftfuzzer -n ftfuzzer_01f23 -c 01f23c39e01d2c739fd8abc69aff9dbf13b46202 -d 2023-12-02T04:13:28+00:00

it builds fine. I didn't look into it further, and this probably isn't an ideal solution since presumably some fuzzers want sanitizers in some contexts.