feat: update and refactoring for move to folder feature (WPB-21155)

[sbakhtiarov]

WPB-21155 [Android]Update “Move to Folder” empty and none-selected states (disable Move button, adjust CTA hierarchy)

https://wearezeta.atlassian.net/browse/WPB-21155

What's new in this PR?

Updating logic and refactoring the Move To Folder feature screen.

• Disable "Move Here" button when no folder selected to avoid moving file to the same folder
• Show "Create Folder" button as primary button if no folder selected
• New text for empty screen if no (root) folders available for selection

Refactoring:

• Moving some logic from composable files to view model
• Move screen parameters to view state
• Extract composable function for content into another file to reduce file length

https://www.figma.com/design/grnVU2vAihHXwYgHryu2xE/Cells---Files?node-id=9021-421573&t=OtIBYIZDGP1jX71t-0

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ohassine]

tbh, I’m not a fan of sending navigation actions through the ViewModel. I feel like we’re overcomplicating things, when it would be much easier and cleaner for reading to just call the navigate command directly from the UI instead of going through the ViewModel and sending the action back.

I also like to keep ViewModels focused on business logic rather than UI stuff like navigation. Otherwise, it can start to feel like we’re mixing responsibilities and adding extra boilerplate.

[ohassine]

The name NavigateToBreadcrumb might be a bit confusing, how about NavigateThroughBreadcrumb ?