fix(quest): clear stale char.complete for re-accepted (prestige) quests

A quest completed in a prior Ascension prestige stays in char.complete.
On re-accept it is active in the log again, but the stale completion flag
was never cleared — and AddFinisher only draws the turn-in '?' when
not char.complete[questId]. So the finisher was suppressed and the quest
showed '(Complete)' with stale objective text while standing at the
turn-in NPC (e.g. Aggression 8334 at Lanthan Perilon 15281).

An active in-log quest is now kept out of char.complete:
- QuestieQuest:AcceptQuest clears char.complete[questId] on accept.
- The async QUEST_QUERY_COMPLETE handler also strips any quest currently
  in QuestiePlayer.currentQuestlog, so the server's completed list can't
  re-flag a re-accepted quest.

Restores the turn-in '?' and normal objective tracking. selene 0 errors;
busted 145 successes / same 7 pre-existing failures.

Modules/Quest/QuestieQuest.lua

@@ -500,6 +500,15 @@ function QuestieQuest:AcceptQuest(questId)
         -- shows again (covers re-doing the quest after abandon or an Ascension prestige).
         QuestieQuest:ClearLootedSpawns(questId)
 
+        -- An accepted quest is active, NOT completed-and-turned-in. On Ascension a quest
+        -- completed in a previous prestige stays in char.complete; when re-accepted the stale
+        -- flag made Questie treat it as done — the turn-in '?' finisher was suppressed
+        -- (AddFinisher requires `not char.complete[questId]`) and it showed "(Complete)".
+        -- Clear it so the quest tracks/finishes normally again.
+        if Questie.db.char.complete then
+            Questie.db.char.complete[questId] = nil
+        end
+
         -- If any of these flags exist, this quest was previously accepted and may
         -- have stale completion state (e.g. complete-then-abandon-then-reaccept leaves
         -- quest.isComplete=true, WasComplete=true). Only check quest-object flags