Skip and log for unrecognised values

[ethan-duckett-brill]

If the EEPROM sees a TS ID that is no longer recognised by the firmware (eg if a value was saved to the EEPROM, then the firmware is updated to a new version that removes said value) then it stops trying to interpret the rest of the EEPROM.

This MR proposes that we should instead just skip this value, log a warning and carry on processing the rest of the EEPROM in this case

[garethpotter]

This seems reasonable, though I wonder if it should be a configurable option? i.e. there could well be use cases where one should fail when there is unexpected data.

[ethan-duckett-brill]

This seems reasonable, though I wonder if it should be a configurable option? i.e. there could well be use cases where one should fail when there is unexpected data.

Good shout, has been changed!

[garethpotter]

I wondered whether this also needed to handle non-Zephyr usage (i.e. not just Kconfig), but I see that as it stands, ThingSetPersistence.cpp is only used by Zephyr, so this is fine.