fix: Handle AppInitStatus with omitted new_feature_info_str

[allenporter]

The approach taken here is:
(1) add an example of this response type to the json examples to exercise the decoder. (This succeeds already, but is just used to record the payload) (2) Add a test for passing the decoded data to the dataclass.

In the future this can be improved with trait tests that use these payloads, but this is a way to do it incrementally for now.

Issue: home-assistant/core#158049

[Copilot]

Pull request overview

This PR fixes an issue where the new_feature_info_str field can be omitted in AppInitStatus responses from some devices, which was causing deserialization failures (issue #158049). The fix makes this field optional and handles the None case appropriately.

Key changes:

• Made new_feature_info_str field optional in AppInitStatus data class
• Added null coalescing in the trait parsing code to convert None to empty string
• Added comprehensive tests including real-world payload examples

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
roborock/data/v1/v1_containers.py	Made new_feature_info_str field optional with default value of None
roborock/devices/traits/v1/device_features.py	Added null coalescing (or "") when passing new_feature_info_str to DeviceFeatures.from_feature_flags()
tests/protocols/testdata/v1_protocol/app_get_init_status2.json	Added real-world test payload demonstrating response without new_feature_info_str field
tests/protocols/snapshots/test_v1_protocol.ambr	Added snapshot expectations for the new test payload showing successful deserialization
tests/test_containers.py	Added test verifying AppInitStatus can be created from dict without new_feature_info_str
tests/test_supported_features.py	Added test verifying DeviceFeatures works correctly with empty new_feature_info_str

---

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