Choice Cells and Menu Cells do not take which properties are available into account for uniqueness

[joeljfischer]

Bug Report

When determining uniqueness, we should take into account what will be displayed to the user, not just all available properties. For example, if a head unit does not support menu cell secondary text but that is the only uniquing factor between two cells, both will still be displayed on a 7.1+ head unit despite them appearing exactly the same.

Reproduction Steps

1. Connect to a 7.1+ module that does not support secondary text
2. Create two menu cells that are identical except for secondary text
3. Display the two menu cells

Expected Behavior

The cells cannot be displayed because they are identical, or the cells have a uniquing factor applied to the primary text

Observed Behavior

The cells are displayed on the head unit identically

OS & Version Information

• iOS Version: n/a
• SDL iOS Version: 7.1+
• Testing Against: Core + Generic HMI

Test Case, Sample Code, and / or Example App

n/a