Reach a stable point where we can cut a release

[stefanbucur]

This is a meta-issue tracking the dependent issues needed so we can cut a release. Tentatively aiming for v0.1.

Work items left

OSS-Fuzz support:

• Add the bazel-rules-fuzzing-test project (Add test project for the Bazel fuzzing rules. google/oss-fuzz#4936).
• Update the Github Actions here to do a CIFuzz run using bazel-rules-fuzzing-test.

Envoy integration:

• Validate that the coverage support is still working.
• Update the Envoy OSS-Fuzz project build script.
• Fix the size bloat caused by the OSS-Fuzz package rule.
• Resolve the disk space and build effort issue caused by the fuzzing instrumentation transition.

Documentation:

• Update the OSS-Fuzz documentation to include Bazel guidance.
• Clarify the asan-replay mode.
• Move the extensibility documentation to a separate page.
• Move the integration instructions to a separate page.
• Document the launcher flags.

Misc:

• Announce the release.

[stefanbucur]

In particular, the release depends on wrapping up the OSS-Fuzz integration: #105 on our end, and submitting google/oss-fuzz#4936.