feat: split off oss-fuzz importer and worker onto their own (#4512)

silo-ing off the oss-fuzz processing so that the special logic it does
can continue working while we make bigger changes to the importer and
worker.
I've given them their own cluster to run in, so we can monitor them
separately (and to make an eventual moving off of the oss-vdb google
cloud project easier).

This is only being deployed to production, since the clusterfuzz pub/sub
only publishes there. We need to be very careful not to impact other
things when we're doing this.

docs: Update REST API docs to clarify HEAD request (#4565)

fix: remove `index-url` from poetry requirements.txt (#4481)

We don't want this to talk to artifact registry
(I'm not 100% sure if this will work as-is)

test: update apitester snapshots (#4457)

The snapshots have changed, probably due to OSV advisories being
changed.
Please review the differences to make sure that they're expected!

fix: add vscode ecosystem and kubernetes (#4393)

test: update vulnerability IDs in integration test (#4357)

chore: use `storage.googlepis.com/[bucket]` URLs everywhere (#4321)

instead of `[bucket].storage.googleapis.com`, per
https://docs.cloud.google.com/storage/docs/access-public-data#api-link

fix: limit number of search indices added to Bugs (#4285)

[openSUSE-SU-2024:12948-1](https://osv.dev/vulnerability/openSUSE-SU-2024:12948-1)
has so many upstream vulns that it made >6500 search_indices, which
(combined with the other fields) was too many indexed properties for
datastore to handle.
Put a limit on the number of search indices populated from
alias/upstreams to avoid this problem.

Add EEF CNA to Test Sources (#4192)

See #4191

docs(blog): fix broken external link (#4133)

This replaces the yuzu link in [Introducing broad C/C++ vulnerability
management
support](https://osv.dev/blog/posts/introducing-broad-c-c++-support/)
with an archived version, since the original repository is no longer
available. The example steps have also been updated to reflect the
current flow verified locally.

This should fix a `404` reported by the markdown-link-check action.  
There's still `429`/`403` issues but those can be fixed in a separate
PR.

---------

Co-authored-by: Rex P <[email protected]>
Co-authored-by: Xueqin Cui <[email protected]>