perf(local): only load advisories that are about the packages being scanned

[G-Rath]

This updates the local matcher to have it skip advisories that don't have at least one affected entry with a package name matching one of the packages being scanned in the current run, which can greatly reduce the peak memory usage for databases like Ubuntu (going from something like 10gb down to 1gb).

Since we cache databases based on their ecosystem only, this does mean subsequent calls to LocalMatcher#MatchVulnerabilities will not give any results for packages that were not present in the first call - while this shouldn't be a problem currently since we handle creating the VulnerabilityMatcher as part of scanning, I've added a basic guard that returns an error if the function is called with any "partial" database cached to catch this (be it on purpose or because of a bug)

This should not impact guided remediation since it explicitly loads the database before doing any work meaning this change won't help it but should also not hurt it

Resolves #2217 (again)

[codecov-commenter]

Codecov Report

❌ Patch coverage is 88.88889% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 67.07%. Comparing base (76887ec) to head (0e31c7c).

Files with missing lines	Patch %	Lines
...al/clients/clientimpl/localmatcher/localmatcher.go	73.68%	4 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2241      +/-   ##
==========================================
+ Coverage   66.53%   67.07%   +0.54%     
==========================================
  Files         169      169              
  Lines       16379    16429      +50     
==========================================
+ Hits        10897    11019     +122     
- Misses       4713     4731      +18     
+ Partials      769      679      -90     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.