fix: add validation for conversation name length

[Avijit-Microsoft]

Purpose

This pull request improves the user experience and validation logic for renaming conversations in the ConversationItem component. The main focus is on enforcing stricter rules for conversation names, providing real-time feedback to users, and ensuring consistency between frontend validation and API calls.

Conversation name validation and UX improvements:

• Added frontend validation to ensure that conversation names are at least 5 characters, contain at least one letter or number, and do not exceed 50 characters before making API calls.
• Updated the input field to display real-time validation errors and enforce a maximum length of 50 characters.
• Added a character counter below the input field to inform users of the maximum allowed length and their current usage.
• Disabled the "Rename" button unless all validation criteria are met, preventing invalid submissions.

Does this introduce a breaking change?

• Yes
• [x ] No

Golden Path Validation

• [x ] I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• [ x] I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• ...

Other Information

[github-actions]

🎉 This PR is included in version 2.2.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀