Isolate singleplayer tossup card collapse state for repeated question IDs

[Copilot]

In singleplayer tossup history, repeated appearances of the same tossup reused identical DOM IDs (question-${_id}), so collapsing one card toggled every matching card. This change scopes collapse/report/star elements to each rendered card instance while preserving the canonical tossup ID for backend actions.

• Singleplayer tossup card ID isolation

  • Updated /client/play/tossups/add-tossup-game-card.js to generate a per-render uniqueId.
  • Derived card-local element IDs from that value (questionId, reportQuestionId, starTossupId) instead of raw _id.
  • Pointed collapse targets and event bindings at those card-local IDs.

• Behavioral impact

  • Collapse/expand now applies only to the clicked card, even when the same tossup appears multiple times in history.
  • Reporting and starring continue to submit/use the original tossup _id.

const uniqueId = `${_id}-${Date.now()}-${Math.random().toString(36).slice(2)}`;
const questionId = `question-${uniqueId}`;

data-bs-target="#${questionId}"
id="${questionId}"

• Fixes From Discord: (see description) #562