Added project_name optional field to user mappings ui (#9)

[satyamMIPL]

A summary of your pull request, including the what change you're making and why.

We have added a new field called project_name in the user mappings to support multiple projects in a single workspace.

• Once user provides this field some string value its should be mapped as moe_project_name in the resulting payload.
• If there is no value provided to this field then resulting payload will not have moe_project_name field at all.
• This is an optional field

Testing

Include any additional information about the testing you have completed to
ensure your changes behave as expected. For a speedy review, please check
any of the tasks you completed below during your testing.

• Added unit tests for new functionality
• Tested end-to-end using the local server
• [If destination is already live] Tested for backward compatibility of destination. Note: New required fields are a breaking change.
• [Segmenters] Tested in the staging environment
• [Segmenters] [If applicable for this change] Tested for regression with Hadron.

Security Review

Please ensure sensitive data is properly protected in your integration.

• Reviewed all field definitions for sensitive data (API keys, tokens, passwords, client secrets) and confirmed they use type: 'password'

New Destination Checklist

• Extracted all action API versions to verioning-info.ts file. example