[CORRUPTED] Synthetic Benchmark PR #26222 - refactor(ui): remove unused components and exports

[tomerqodo]

Benchmark PR calcom#26222

Type: Corrupted (contains bugs)

Original PR Title: refactor(ui): remove unused components and exports
Original PR Description: ## What does this PR do?

This PR removes unused components and exports from the UI package to reduce codebase size and improve maintainability. All removed components were verified to have zero imports or usage in the codebase.

Components Removed:

• UpgradeOrgsBadge - Badge component with no usage
• InputFieldWithSelect - Form component only used in tests
• Stepper - Step component with no usage
• FormStep - Step component with no usage
• RangeSlider - Slider component with no usage
• RangeSliderPopover - Slider component with no usage
• Slider - Slider component (misnamed index.tsx file) with no usage
• NavigationItem - Navigation component from UI package (different from shell NavigationItem)
• AddressInputNonLazy - Address component export (only used in removed test file)

Exports Removed:

• HintsOrErrors export (component kept, used internally by TextField)
• FieldsetLegend, InputGroupBox, InputLeading from form inputs
• DropdownMenuRadioGroup, DropdownMenuRadioItem, DropdownMenuGroup, DropdownMenuTriggerItem from dropdown

Test Files Cleaned:

• Removed BookingFields.test.tsx that used AddressInputNonLazy
• Updated input.test.tsx to remove InputFieldWithSelect test

Impact:

• 9 files deleted
• 15 exports removed
• ~560 lines of unused code removed
• Zero breaking changes (all removed components verified as unused)

Visual Demo (For contributors especially)

N/A - This is a code cleanup PR with no visual changes. All removed components were unused and had no impact on the UI.

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• 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?

Verification Steps:

1. Run yarn type-check:ci --force to ensure no type errors
2. Run yarn lint:fix to ensure no linting errors
3. Verify the application builds successfully: yarn build
4. Run existing test suite to ensure no regressions: yarn test
5. Manually verify that all UI components still work as expected

What was verified:

• All removed components have zero imports in the codebase
• No production code references the removed components
• Internal dependencies preserved (e.g., HintsOrErrors still used by TextField)
• Type exports maintained
• All test files updated appropriately

Expected Result:

• Application builds and runs without errors
• No functionality changes (all removed components were unused)
• Reduced bundle size due to removed unused code

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
• Code removal, no new code added
• I have checked if my changes generate no new warnings
• Verified with yarn lint:fix and yarn type-check:ci --force
  Original PR URL: refactor(ui): remove unused components and exports calcom/cal.com#26222

[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 #26222 - refactor(ui): remove unused components and exports". 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

[github-actions]

This PR has been marked as stale due to inactivity. If you're still working on it or need any help, please let us know or update the PR to keep it active.