[CORRUPTED] Synthetic Benchmark PR #24829 - feat: add banner for upgrade when using company email

[tomerqodo]

Benchmark PR calcom#24829

Type: Corrupted (contains bugs)

Original PR Title: feat: add banner for upgrade when using company email
Original PR Description: ## What does this PR do?

• Adds a new banner component that detects when users are using company emails but haven't set up an organization
• The banner encourages users to explore the organizational plan for better team collaboration
• Implements a dismissible UI with an "Upgrade" button that directs users to the organization setup flow

Visual Demo (For contributors especially)

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code.
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

1. Log in with a company email address (e.g., user@company.com) that isn't part of an organization
2. Navigate to Settings > My Account
3. Verify the banner appears with the correct messaging
4. Test the "Dismiss" button to ensure it removes the banner
5. Test the "Upgrade" button to ensure it redirects to the organization setup flow
6. Verify the banner doesn't appear for personal email domains or users already in organizations

Checklist

• I have read the contributing guide
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have checked if my changes generate no new warnings
  Original PR URL: feat: add banner for upgrade when using company email calcom/cal.diy#24829

Issues Breakdown

• Total Issues: 7
• Easy: 4
• Medium: 2
• Hard: 1

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "[CORRUPTED] Synthetic Benchmark PR #24829 - feat: add banner for upgrade when using company email". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit