Add OSS-Fuzz support to the Bazel fuzzing rules.

[stefanbucur]

The support includes (a) a repository rule that extracts OSS-Fuzz environment information and makes it available hermetically in a @rules_fuzzing_oss_fuzz repo, and (b) a new target in the cc_fuzz_test macro that packages a fuzz test and its dependencies in the OSS-Fuzz format.

[stefanbucur]

I still need to update the documentation, but I wanted to first validate with you the implementation, to make sure it properly observes OSS-Fuzz's contracts @inferno-chromium @oliverchang

[stefanbucur]

Starting another thread to discuss testing: IMO, it would be nice if there was a way to make sure the code works correctly end-to-end on the latest versions of these rules and OSS-Fuzz.

@inferno-chromium @oliverchang do you think we should have tests inside the OSS-Fuzz repo, here, or both? If so, any thoughts on how to best test these? My own (manual) testing resorted to create a dummy project (like this) and then making sure the examples in this repo build under that project. Is there a better way to do this during CI?

[oliverchang]

nice!

[stefanbucur]

Thanks for all the feedback! PTAL.

[stefanbucur]

Starting another thread to discuss testing: IMO, it would be nice if there was a way to make sure the code works correctly end-to-end on the latest versions of these rules and OSS-Fuzz.

@inferno-chromium @oliverchang do you think we should have tests inside the OSS-Fuzz repo, here, or both? If so, any thoughts on how to best test these? My own (manual) testing resorted to create a dummy project (like this) and then making sure the examples in this repo build under that project. Is there a better way to do this during CI?

Bumping this up, in case you have any suggestion.

[oliverchang]

Starting another thread to discuss testing: IMO, it would be nice if there was a way to make sure the code works correctly end-to-end on the latest versions of these rules and OSS-Fuzz.
@inferno-chromium @oliverchang do you think we should have tests inside the OSS-Fuzz repo, here, or both? If so, any thoughts on how to best test these? My own (manual) testing resorted to create a dummy project (like this) and then making sure the examples in this repo build under that project. Is there a better way to do this during CI?

Bumping this up, in case you have any suggestion.

Perhaps we can have a GitHub action for this repo which checks out OSS-Fuzz at the latest revision and builds the test project? Seems like something that would fit better in this repo.

[stefanbucur]

Starting another thread to discuss testing: IMO, it would be nice if there was a way to make sure the code works correctly end-to-end on the latest versions of these rules and OSS-Fuzz.
@inferno-chromium @oliverchang do you think we should have tests inside the OSS-Fuzz repo, here, or both? If so, any thoughts on how to best test these? My own (manual) testing resorted to create a dummy project (like this) and then making sure the examples in this repo build under that project. Is there a better way to do this during CI?

Bumping this up, in case you have any suggestion.

Perhaps we can have a GitHub action for this repo which checks out OSS-Fuzz at the latest revision and builds the test project? Seems like something that would fit better in this repo.

Sounds great - let's move the conversation to #105. There are a few details to figure out I think.