Improve resource name validation

[callmevladik]

The Portal UI needs to be enhanced by applying restrictions on the lengths of codebase and codebase branch names. Specifically, both the codebase name and the codebase branch name should be limited to a maximum of 30 symbols. This change aims to standardize naming conventions and improve data management within the system.

Acceptance Criteria
The codebase name field in the UI restricts input to a maximum of 30 symbols.
The codebase branch name field in the UI restricts input to a maximum of 30 symbols.
When a user attempts to enter names longer than 30 symbols, the system should display an informative error message.
Ensure that these restrictions are applied consistently across all relevant forms and interfaces in the Portal UI.
Testing is conducted to confirm that the restrictions are enforced and that error messages are displayed appropriately.
Documentation is updated to reflect the new restrictions on name lengths.

Important Note: It is crucial to validate the current naming size with the QA team to ensure that this change aligns with existing test cases and does not adversely affect current functionalities.

---

The task focuses on enhancing the UI interface by displaying validation logs during the CDStage creation process. The backend already performs validation for CDStage creation, and these validations are included in the response. The objective is to ensure these validation logs are effectively presented in the UI to provide immediate feedback to users. This feature will aid in debugging and streamline the creation process by allowing users to correct any issues in real-time.

Acceptance Criteria

1. Validation Log Integration: Validation logs from the CDStage creation response are displayed in the UI.
2. User Feedback: Users should receive immediate feedback on any validation errors encountered during the CDStage creation process.
3. UI Design: The display of validation logs should be intuitive and seamlessly integrate with the existing UI design.
4. Error Visibility: Validation errors must be prominently displayed to ensure they are not overlooked by the user.
5. Actionable Errors: Where possible, errors should guide the user on how to resolve the issue.
6. Performance: The integration of validation logs should not adversely affect the UI performance.