fix(duplicate): projectManager not populated in projectPayloadData on duplicate project page

[sujalkalauni]

Summary

In DuplicateProject.tsx, the projectManager field was correctly fetched
from the API and stored in local state, but was never assigned in
projectPayloadData — the object actually sent to create the duplicate project.

This meant every duplicated project silently lost its Project Manager.

Fix

Added the missing assignment alongside the existing projectOwner and
leadArchitect fields:

projectManager: project._embedded?.projectManager?.email ?? '',

Related

Fixes #1559

[amritkv]

Hey @sujalkalauni !
This change doesn't seem to be working.
There are 2 keys for the same field, i.e. ProjectResponsible and ProjectManager. Please check and use the correct one here.

[sujalkalauni]

Thanks for the review @amritkv. I can see both projectResponsible (top-level string) and projectManager (User object in _embedded) in the Project type. I followed the same pattern as leadArchitect and projectOwner which also use _embedded.
Could you help me understand which one maps to the Project Manager field in the UI? Should I use project.projectResponsible instead?

[amritkv]

Hey @sujalkalauni !
Please have a quick look at Add Project and Edit Project files for the clarifications and how the field is handled.

[sujalkalauni]

Thanks @amritkv, checked both AddProject and EditProject. EditProject made it clear that the UI state is named projectManager but the actual API payload key is projectResponsible. Updated the initial state and payload accordingly and cleaned up a duplicate line and a typo that crept in during editing. Please have another look.