Fixing issue of scroll paddings in Navigation Drawer

[muraliSingh7]

This PR fixes the issue #9026

Screenshot:

[greptile-apps]

PR Summary

This PR fixes scroll padding issues in the Navigation Drawer by ensuring proper scrollbar visibility and preventing overlap with navigation items.

• Removed scrollHide={true} from ScrollWrapper in packages/twenty-front/src/modules/navigation/components/MainNavigationDrawerItems.tsx to show scrollbar
• Added theme-based spacing and width calculations in packages/twenty-front/src/modules/ui/navigation/navigation-drawer/components/NavigationDrawerItem.tsx for better layout
• Implemented margin-right in packages/twenty-front/src/modules/ui/navigation/navigation-drawer/components/NavigationDrawerSectionTitle.tsx to prevent scrollbar overlap
• Improved text overflow handling with ellipsis in navigation items
• Optimized spacer component rendering to appear only when needed

_{💡 (4/5) You can add custom instructions or style guidelines for the bot here!}

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

[ehconitin]

Thanks, @muraliSingh7, this is not the correct approach. Here we are changing the NavigationDrawerItems width i.e. 204px according to Figma designs.
Thanks for the effort, I will be fixing it in #9141
Closing this PR ;)

[muraliSingh7]

@ehconitin Thank you for your feedback. I acknowledge that my approach didn't align with the design specifications, and I appreciate your clarification. However, I followed the current pattern established by the core maintainers, where fixed values for width are used. If there's a preference to avoid such fixed values, I would have appreciated a more collaborative discussion on how we can improve this approach going forward.

I believe it would be more productive to ask whether we can explore alternatives rather than closing the PR immediately. It's important to recognize the effort that contributors put in, and fostering a supportive dialogue can lead to better outcomes for everyone.

[ehconitin]

@muraliSingh7
Thank you for the PR. While I did ask you to create it to test the behavior, the implementation needs to follow specific requirements that were talked about internally. We are experimenting with different scroll behavior and padding configurations.

Given these constraints and internal priorities, I'll implement this in #9141. I should have told you more about these requirements when you offered to help.

Please understand that maintainers' decisions are based on project requirements rather than personal preferences.

There are many issues to be picked, sorry for this one ;)

Thanks for understanding!