feat: Implement channel and project name validation, enhance error ha…

[dev-bre]

This pull request introduces improved validation and error handling for creating channels and projects, as well as refactors how events are created to use names instead of IDs for project and channel lookups. The changes enhance user feedback, enforce stricter naming rules, and simplify the event creation API.

Frontend improvements:

• Added validation for channel and project names to only allow letters, numbers, hyphens, and underscores, with immediate feedback for invalid names in CreateChannelDialog.tsx and CreateProjectDialog.tsx. [1] [2]
• Enhanced error handling for channel and project creation: now displays specific error messages returned from the backend instead of a generic failure message. [1] [2]

Backend validation and API changes:

• Added server-side validation for channel and project names to enforce allowed characters in channel.go and project.go. [1] [2]
• Refactored event creation to accept project and channel names instead of IDs, updating the handler and service logic to look up entities by name and user/project relationship. [1] [2] [3]
• Added new repository methods to find projects by user and name, and channels by project and name, updating repository interfaces and implementations accordingly. [1] [2] [3] [4]…ndling, and add repository methods for name lookup

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Related Issue

Closes #(issue number)

How Has This Been Tested?

Describe the tests you ran and how to reproduce them.

Screenshots (if applicable)

Add screenshots to help explain your changes.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes