refactor: Unique names for the pattern {parent_banch_name}.{branch_name}

[jdacoello]

Addresses the issue #797 .

[erikbosch]

MoM:

• Daniel presented the change
• Deprecation included so we could release it as part of a minor release
• Erik: Deprecation not needed if we intend to release it only as 6.0
• Please review!

[erikbosch]

I took a quick look. In general I think the approach of removing the "switch" sub-branch makes sense.

A side-note for switches. In VSS we typically have for each seat attribute (e.g. headrest tilt) have 3 data, position (absolute value in mm/degrees or relative in percent) and two "switches" for more/less. In Android VHAL they have a partially different representation with two data, position and "speed", the advantage is that you can represent how fast you want the seat to move.

Operation	Android	VSS
Move to a specific position	Set SEAT_BACKREST_ANGLE_1_POS	Set Backrest.Recline
Move forward	Set SEAT_BACKREST_ANGLE_2_MOVE to a positive value	Set Backrest.IsReclineForwardSwitchEngaged to True
Move backward	Set SEAT_BACKREST_ANGLE_2_MOVE to a negative value	Set Backrest.IsReclineBackwardSwitchEngaged to True

[jdacoello]

A side-note for switches... you can represent how fast you want the seat to move

@erikbosch Interesting that you mention this feature. Specifying custom arguments for the properties is natively supported by the GraphQL Schema Language.

type Seat {
  isReclineForwardSwitchEngaged(mechanismSpeed: SeatReclineSpeed = MEDIUM): Boolean
}

enum SeatReclineSpeed {
  SLOW
  MEDIUM
  FAST
}

You can see how things are still connected, even when they are maintained separately. In current VSS, we would need two different data points (or an struct) to convey the same meaning.