Tracker: scan error notifications include packages listed in the repository's ignore list #4879

Describe the bug
Repository scan-error emails include errors for packages that the repository's artifacthub-repo.yml explicitly lists under ignore. Per @tegioz in the Slack thread (https://cloud-native.slack.com/archives/C0103CTR3RB/p1788962271486889), this is because the ignore filter is applied later in the workflow (at package-registration decision time), while the errors originate earlier during the per-artifact-kind package extraction. The ignore behavior itself works: the package is correctly not indexed (the API returns 404 for it).

To Reproduce

1. Helm repository argo (repositoryID 05f5fe20-d21b-4413-8327-715958b51bde), metadata at https://argoproj.github.io/argo-helm/artifacthub-repo.yml, contains:

   ignore:
     - name: argo-lite

2. The repository's index.yaml still contains historical argo-lite entries (a chart last published years ago), so the scanner encounters it during extraction.
3. The repository owner receives scan-error emails containing:

   error getting logo image https://raw.githubusercontent.com/argoproj/argo/master/saas/axops/src/ui/src/assets/favicon/favicon-32x32.png: unexpected status code received: 404 (package: argo-lite version: 0.1.0)
   

Expected behavior
Errors for ignored packages are filtered out of owner notifications (or the ignore filter is applied before or during extraction), since owners cannot and should not act on packages they have excluded.

Additional context
Filed at @tegioz's request in the Slack thread above. Companion feature request about historical-version errors filed separately.