[Nu-1889] provide an unique validation message to the scenario labels

[Dzuming]

Describe your changes

Checklist before merge

• [x] Related issue ID is placed at the beginning of PR title in [brackets] (can be GH issue or Nu Jira issue)
• [ ] Code is cleaned from temporary changes and commented out lines
• [ ] Parts of the code that are not easy to understand are documented in the code
• [x] Changes are covered by automated tests
• [ ] Showcase in dev-application.conf added to demonstrate the feature
• [x] Documentation added or updated
• [ ] Added entry in Changelog.md describing the change from the perspective of a public distribution user
• [ ] Added MigrationGuide.md entry in the appropriate subcategory if introducing a breaking change
• [ ] Verify that PR will be squashed during merge

Summary by CodeRabbit

Release Notes

• New Features

  • Enhanced validation for scenario labels, ensuring uniqueness and appropriate error messaging for duplicate or excessively long labels.
  • Introduction of a new Activities panel for better organization of scenario activities.
  • New scenario labels feature to improve scenario management and retrieval.

• Bug Fixes

  • Improved error handling and user feedback for label input validation.

• Documentation

  • Updated changelog to reflect new features, improvements, and breaking changes in version 1.18.

[coderabbitai[bot]]

📝 Walkthrough

📝 Walkthrough

## Walkthrough This pull request introduces enhancements to the label input validation in the Cypress end-to-end tests and the `ScenarioLabels` component. It includes new validation checks for duplicate and excessively long labels, improving user feedback in the testing framework. Additionally, the `ScenarioLabels` component has been updated with new functions for label uniqueness validation and performance optimizations. The changelog has also been updated to document these changes and other enhancements in version 1.18. ## Changes | File Path | Change Summary | |------------------------------------------------|-------------------------------------------------------------------------------------------------------| | designer/client/cypress/e2e/labels.cy.ts | Added validation checks for duplicate and long labels in Cypress tests; verified error messages. | | designer/client/src/components/toolbars/scenarioDetails/ScenarioLabels.tsx | Introduced `labelUniqueValidation` function; refactored `isInputInSelectedOptions` for performance; updated `validateInput` for label uniqueness validation. | | docs/Changelog.md | Updated to reflect new features, improvements, and breaking changes in version 1.18, including new methods and enhancements. | ## Possibly related PRs - #7166: The changes in this PR enhance the validation logic for label inputs, which is closely related to the validation checks introduced in the main PR for ensuring label uniqueness and handling errors in the `ScenarioLabels` component. ## Suggested reviewers - arkadius > 🐰 In the meadow where we play, > New labels bloom, bright as the day. > Unique and long, they must be right, > With tests that catch them in their flight. > Hooray for changes, let’s all cheer, > For better labels, bring us near! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.