Add MQTT location response tests

[augard]

Summary

• add VehicleMQTTLocationResponseTests to cover merged timestamp decoding
• verify valid timestamp parsing yields expected UTC components even when location is null
• ensure invalid timestamp formats throw and round-trip formatter via MergedDateFormatter

Testing

• Not run (not requested)

[github-actions]

There is a problem with the Gemini CLI PR review. Please check the action logs for details.

[augmentcode]

🤖 Augment PR Summary

Summary: Adds test coverage for MQTT location responses and merged timestamp decoding.

Changes:

• Add VehicleMQTTLocationResponseTests to exercise latestUpdateTime parsing (yyyyMMddHHmmss) and Location: null decoding.
• Assert the parsed Date matches expected UTC components.
• Ensure invalid timestamp formats throw and validate MergedDateFormatter round-trip behavior.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

[Copilot]

Pull request overview

Adds a new XCTest suite to validate decoding of MQTT “merged” timestamp strings for VehicleMQTTLocationResponse, including behavior when the nested Location payload is null.

Changes:

• Add coverage for decoding a valid latestUpdateTime merged timestamp and asserting UTC date components.
• Add a negative test ensuring invalid merged timestamp strings fail decoding.
• Add a MergedDateFormatter round-trip test (string → date → string).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.