Background: When the CX desktop editor loads, the "page" URL parameter is always set. During editor initialization, a request is being sent to fetch the draft translation for the given page, if one exists for the current user. If no draft exists, the backend checks for conflicting translations. If such translation is found, the UI should be notified, in order to block this translation. Finally, if neither a draft nor a conflicting translation has been found, nothing is returned. The UI is handling this case as new translation.
The issue: In the case of conflicting translation, the whole translation is still being returned, even if it's not needed in the UI. On the other hand, the "translatorName" and the "translatorGender" properties are also returned for draft translations, while they are only needed when a conflict exists (that means no draft has been found for the current user).
This task proposes to align the returned payload with the needed information in the client side, for smaller responses and more-straightforward implementation.
