Remove opportunity specific code on Kanban

[charlesBochet]

In this PR:

• clean board from opportunity specific logic
• remove in place creation in board
• trigger creation in right drawer instead

[greptile-apps]

PR Summary

This PR removes opportunity-specific code from the Kanban board implementation, making it more generic and reusable across different object types.

• Removed RecordBoardColumnNewOpportunity.tsx component and replaced with generic record creation approach
• Simplified useAddNewCard hook by removing company-related logic and SingleRecordPicker dependencies
• Removed isOpportunity field from NewCard type in recordBoardNewRecordByColumnIdComponentFamilyState.ts
• Cleaned up unused opportunity-related imports and checks in RecordBoardColumnCardsContainer.tsx
• Note: Several components still import unused opportunity-related hooks (useIsOpportunitiesCompanyFieldDisabled) that should be removed

_{8 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

style: company field is still present in the state but company-related functionality has been removed. Consider removing this field.

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ Error: Object metadata item "what" cannot be found in an array of 39 elements /object/what/hah View Issue

_{Did you find this useful? React with a 👍 or 👎}