[NRT-591] Surface duplicate anki_id suggestion error + redesign bulk suggestion summary

[RisingOrange]

Related issues

• Closes NRT-591

Proposed changes

When a user submits a new-note suggestion for a note whose anki_id already exists in the deck on AnkiHub (note created + auto-accepted, then edited and re-suggested before a sync), the server rejects it with "A deck can't contain multiple notes with the same anki_id.". Previously this failure was effectively hidden (single → raw showInfo; bulk → an uncategorized blob in the plain-text summary). This PR surfaces it and lets the user recover.

Detection (main/suggestions.py)

• ANKIHUB_DUPLICATE_ANKI_ID_ERROR constant + parse_duplicate_anki_id_error() — tolerates the backend's DRF-normalized payload (list-wrapped/stringified: reads conflicting_ankihub_id[0], compares conflicting_note_deleted[0] == "True", not truthiness).
• Resubmit core: _new_note_to_change_suggestion() converts the already-built NewNoteSuggestion into a ChangeNoteSuggestion keyed by the conflicting ah_nid and lets the server diff — no remote fetch, no AnkiHub-DB write. resubmit_new_note_as_change_suggestion() (single) and resubmit_new_notes_as_change_suggestions_in_bulk() (one batched call).
• suggest_notes_in_bulk now returns already_in_deck_by_nid on the result; soft-deleted conflicts are routed to the existing deleted-on-AnkiHub category instead (a change suggestion would 404 a tombstoned note).

Scenario 1 — single suggestion (gui/suggestion_dialog.py)

• New NoteAlreadyExistsDialog (info icon, Cancel / Send as change suggestion). The suggestion dialog closes and the modal shows over the editor; on success → toast; soft-deleted conflict → existing "deleted from AnkiHub" dialog; missing conflicting id (older server) → falls back to today's generic error.

Scenario 2 — bulk suggestion summary (gui/bulk_suggestion_summary_dialog.py)

• Replaces the plain-text showText summary with a real BulkSuggestionSummaryDialog, shown for all outcomes (full redesign): colored counts, bold (N) category titles, a new "Other errors" bucket with a community.ankihub.net/c/support link, and the redundant "All notes with failed suggestions" block removed.
• New interactive "Notes already in this deck" action box: Resubmit (one batched create_suggestions_in_bulk call) / Ignore; Close/X disabled until resolved; "Updated" badges on changed categories; a hard resubmit failure re-enables Close (no dead-end).

Analytics (structlog → Datadog) — single: duplicate_note_error_dialog_shown, duplicate_note_resubmitted_as_update_suggestion; bulk: bulk_duplicate_note_error_dialog_shown, bulk_duplicate_note_resubmitted_as_update_suggestion.

How to reproduce

As a maintainer on staging:

1. Create a new note in Anki using one of your deck's AnkiHub note types and Suggest it (auto-accepts so the note is created on AnkiHub).
2. Don't sync. Edit the same note and suggest it again.
3. Before: the failure was hidden (single: a raw error; bulk: an uncategorized failure count).
4. After: single → "Note already exists in this deck" dialog with Send as change suggestion; bulk → the note lands in the "Notes already in this deck" action box with a Resubmit as change suggestions button.

Tests: pytest tests/addon -k "BulkSuggestionSummaryDialog or MaybeHandleNoteAlreadyExists or ParseDuplicate or NewNoteToChange or OnSuggestNotesInBulkDone or already_in_deck".

Screenshots and videos

Redesigned Bulk Suggestion Summary dialog.

Default (dark) — Summary, categorized submission issues, and the full-bleed "Action required" band:

After resubmitting — the band is removed and the Summary updates with an "Updated" badge (failed count drops accordingly):

Ignored — user dismissed the action; the band collapses to a muted note and Close is enabled:

Light mode:

[ddevdan]

There's this medium bug that claude flagged where if you submit a note with image, then change the image and try to submit again, the image breaks

Single-note resubmit submits stale media filenames

  `resubmit_new_note_as_change_suggestion` rebuilds the suggestion from the **in-memory** `note`, but the failed `suggest_new_note` renamed media to hashed names via raw SQL on the DB only (`_update_media_names_on_notes` → `media_utils.py:9`) — the
  in-memory note is stale. So if new media is added during the edit, the change suggestion references the **original** filename, which was never uploaded under that name → broken image for everyone who syncs. Silent, and auto-accept (the maintainer
  trigger) skips review.

  Bulk path is safe — it reuses the post-rename DTO. Not hit by the canonical NRT-591 repro (text-only edit, no rename), which is why tests stayed green.

  **Fix** (one line in the single path):
  ```python
  # Failed new-note submit renamed media in the DB only, not the in-memory note. Reload
  # so the change suggestion carries the uploaded (hashed) names, not the stale originals.
  note = aqt.mw.col.get_note(note.id)

screen-capture.10.webm

Solution:

++ b/ankihub/main/suggestions.py
     @@ -547,6 +547,11 @@ def resubmit_new_note_as_change_suggestion(
          """Resubmit a single note (whose new-note suggestion hit the duplicate-anki_id
          error) as a change suggestion for the existing note. Media was already renamed and
          uploaded by the failed new-note submit, so it is not re-uploaded here."""
     +    # The failed new-note submit renamed media to hashed names directly in the DB (raw
     +    # SQL, see `_update_media_names_on_notes`) without touching the in-memory note the
     +    # caller is holding. Reload so the change suggestion carries the uploaded (hashed)
     +    # media names rather than the stale originals (which were never uploaded).
     +    note = aqt.mw.col.get_note(note.id)
          new_note_suggestion = _new_note_suggestion(note, ah_did, comment, filters=filters)
          if new_note_suggestion is None:
              return ChangeSuggestionResult.NO_CHANGES

[RisingOrange]

@ddevdan Good catch!

[ddevdan]

LGTM