Enable the 'read' and 'acknowledgment' status of parent card depends of child card 'read' and 'acknowledgment' status

[freddidierRTE]

The objective is to introduce a feature enabling a parent card to have the card not read and not acknowledge if a child card is published . To implement this functionality, a new field will be added to the card structure.

The proposed solution involves incorporating an 'action' field within the card, structured as an array of predefined actions. The initial predefined action to be introduced is

'PROPAGATE_READ_ACK_TO_PARENT_CARD"

--> to be decided

Anticipating future needs, additional predefined actions may be introduced, such as 'PROPAGATE_READ_ACK_TO_PARENT_CARD_FOR_PUBLISHER' and 'KEEP_READ_AND_ACK_OF_PREVIOUS_CARD_VERSION.'

Moreover, this new 'action' field could potentially replace the existing 'keepChildCards' field, transforming it into an action labeled 'KEEP_CHILD_CARDS_FROM_PREVIOUS_CARD'

The use of this new field is to be done on the front code :

• when a card is read by user , it should set read in the back to the card and child cards with value PARENT_CARD_READ_ACK_IF_CARD_READ_ACK
• when a card is ack by user , it should ack the card in the back and the child cards with value PARENT_CARD_READ_ACK_IF_CARD_READ_ACK

On the front side :

• a card is consider ack if the card is ack and all the child card with PARENT_CARD_READ_ACK_IF_CARD_READ_ACK are ack
• a card is consider read if the card is read and all the child card with PARENT_CARD_READ_ACK_IF_CARD_READ_ACK are read

Impact on lightCard and Card Components