Review the relatedParty property in Service Order

Currently, when Service Orders are created, the relatedParty property is populated by the user's information.

The relatedParty property comprises:

• id
• href
• name
• role
• uuid
• extendedInfo

The current behaviour is:

• id: {username}
• name: {username}
• role: REQUESTER,
• extendedInfo: {user email}
• uuid: {new generated identifier}

Also, Order Patching adds another entity in relatedParty with the same properties and a new uuid.

Intended behaviour

During the creation of the Service Order, the relatedParty entity needs to be populated with the registered user's identifier from the Individual database. (Check if exists, else create)

During Service Order Patching, if the user is the same, nothing happens in the relatedParty list. If the user is different, add to the relatedParty list with role:"MODIFIER"