fix(editor): cap quest count at 4096 and object count at 100k on load

A stale autosave or hand-edited JSON could carry an unbounded list:
- 100k quests would emit 100k quest_template + queststarter/ender
  INSERTs (huge SQL, slow validate, slow chain walks).
- 1M+ objects bloats the M2 instance SSBO and drags editor framerate
  to single digits.

Caps mirror the 256-waypoint cap added in the previous batch — log
a warning and drop the rest so the editor stays responsive.

tools/editor/quest_editor.cpp

@@ -77,7 +77,18 @@ bool QuestEditor::loadFromFile(const std::string& path) {
         quests_.clear();
         uint32_t maxId = 0;
 
+        // Cap total quest count — a stale autosave or hand-edited file
+        // could carry thousands of empty quests, each emitting a
+        // quest_template INSERT (and queststarter/questender + chain
+        // walks) on export. 4096 covers any realistic zone.
+        constexpr size_t kMaxQuests = 4096;
+
         for (const auto& jq : arr) {
+            if (quests_.size() >= kMaxQuests) {
+                LOG_WARNING("Quest cap reached (", kMaxQuests,
+                            ") — remaining entries dropped");
+                break;
+            }
             Quest q;
             q.id = jq.value("id", 0u);
             q.title = jq.value("title", "Untitled");