fix(quest): stabilize mission order display and improve hunt mission update mapping

[boscv]

Motivation

• Quest mission progress could remain at 0/x for some slots on certain servers when update packets used identifiers that did not directly match stored mission keys.
• quest list mission order could appear inconsistent due to hash key iteration order, causing confusion versus in-client ordering.

Changes

• src/Network/Receive.pm

  • Added a guard in quest_update_mission_hunt to skip processing when the quest is not present in questList.
  • Preserved existing mission resolution paths (hunt_id direct match, mob_id direct match, and cross-lookup).
  • Added a fallback resolver that maps by derived mission index when direct identifier matching fails:
    • mission_index = hunt_id - (questID * 1000)
    • accepts both mission_index and mission_index - 1 to handle index variance.
  • Added a final guard to skip updates when no valid mission_id can be resolved, preventing writes to invalid mission entries.

• src/Commands.pm

  • Updated quest list mission rendering to sort missions by:
    1. mission_index (ascending, default fallback 9999)
    2. mission key (mobID) as deterministic tie-breaker
  • This keeps mission display order stable and aligned with packet/client intent.

Impact

• Reduces cases where only some mission slots update while others remain at 0/x.
• Makes quest mission display deterministic and less confusing.
• Keeps behavior backward-compatible by applying fallback logic only when standard matching fails.

Testing

• Validation performed through code-path review and targeted local quest flow checks.