Remove Innovation flow title/description from innovation flow management

Walkthrough

The pull request introduces significant updates to the translation.en.json file, primarily focusing on renaming terms and enhancing clarity in user-facing text across various sections of the application. Additionally, it modifies the InnovationFlowSettingsDialog component to streamline its functionality by removing unnecessary properties and replacing components to focus on collaboration tools. The InnovationFlowDragNDropEditor component is also updated to improve the layout of the drag-and-drop interface, transitioning to a flexbox layout while maintaining existing functionality.

Changes

File Path	Change Summary
`src/core/i18n/en/translation.en.json`	Updated strings for clarity, renamed "Innovation Flow Settings" to "Manage Flow", and revised button tooltips.
`src/domain/collaboration/InnovationFlow/InnovationFlowDialogs/InnovationFlowSettingsDialog.tsx`	Removed `authorization` property, replaced `InnovationFlowProfileBlock` with `InnovationFlowCollaborationToolsBlock`, and reorganized props.
`src/domain/collaboration/InnovationFlow/InnovationFlowDragNDropEditor/InnovationFlowDragNDropEditor.tsx`	Replaced `ScrollableCardsLayoutContainer` with a `Box` component for a flexbox layout, improving item display while preserving functionality.

Possibly related PRs

#6998: This PR modifies the same translation.en.json file, focusing on different sections but indicating ongoing changes to the translation structure.
#7096: This PR also updates the translation.en.json file, reflecting changes in translations that may relate to the overall rebranding or simplification of terms.
#7127: This PR includes changes to the useInnovationFlowSettings hook, which may relate to the broader context of managing innovation flows, aligning with the terminology updates in the main PR.
#7130: Similar to #7127, this PR modifies the useInnovationFlowSettings hook, enhancing the refetching mechanism, which could be relevant to the changes in managing innovation flows.
#7136: This PR also updates the useInnovationFlowSettings hook, indicating ongoing improvements in the innovation flow management, which aligns with the main PR's focus on terminology and clarity.
#7224: While primarily focused on styling fixes, this PR may relate to the overall user interface improvements that the main PR aims to achieve through clearer terminology in the translation files.

Suggested labels

client, translations

📜 Recent review details

**Configuration used: .coderabbit.yaml** **Review profile: CHILL**

📥 Commits

Reviewing files that changed from the base of the PR and between 45420bf664ffbe0cdb3c7a871783fdeafc8e6d4c and 0c4aa04ebdc7d42dffacbb04ef80e7bdcc1c81f7.

📒 Files selected for processing (1)

* `src/core/i18n/en/translation.en.json` (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

src/core/i18n/en/translation.en.json (1)

Pattern `src/**/*.json`: Review the JSON files for correct syntax and structure. Ensure that the configuration and data are accurate and follow the project's standards. Check for sensitive data exposure and ensure that the data is properly validated.

🔇 Additional comments (1)

src/core/i18n/en/translation.en.json (1)

`1066-1069`: **LGTM! The terminology changes improve clarity.** The changes simplify the UI by removing redundant "Innovation" prefix while maintaining clear context. The consistent terminology across these related UI elements improves the user experience.

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. ### 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.

alkem-io / client-web