Integrating with OSS-Fuzz

This is a follow-up to https://github.com/KhronosGroup/SPIRV-Cross/issues/1238

I'm reaching out to ask if spirv-cross would be happy to integrate with OSS-Fuzz? OSS-Fuzz is a continuous fuzzing set up for important open source projects and has helped find a lot of memory corruption issues in various projects.

In https://github.com/google/oss-fuzz/pull/12708 I did an initial integration of SPIRV-cross and would be happy to submit a further set of harnesses if you're happy to integrate. The goal would be to have good coverage of SPIRV-cross.

In order to integrate, the only thing needed is one or more maintainer emails that would be happy to receive notifications for any issues find, including detailed reports with stacktraces, reproducers and more. The project will also show up on https://introspector.oss-fuzz.com/ where it's convenient to track e.g. fuzzing code coverage of the projects in OSS-Fuzz.

Review the follow-up issue #1238 and the initial integration in OSS-Fuzz PR #12708. Confirm whether SPIRV-Cross should join OSS-Fuzz and which maintainer emails should receive notifications; done means an accepted integration with harnesses and coverage tracking available through OSS-Fuzz.

Written by the indexing model from the issue text.