Code Quality: Introduce details layout columns generator phase 1

[0x5bfa]

Summary

As of now, you have to add literally 250 lines only for one column when you are adding a new one (you can see git column introduction PR). We are introducing columns generator to mitigate that situation.

Task Checklist

• Clean up
• Introduce details layout columns generator

Steps To Validate Changes

1. Launch the app
2. Go to a folder
3. Resize some columns
4. Hide some columns
5. Go to another folder
6. See the columns you hid are shown in that folder
7. Go to git folder
8. See git columns appear

If nothing happen, you confirmed layout settings for each page are stored correctly in user_settings.db, hide/show operation is working properly, the app is able to fetch settings from the database and use them in an actual layout.

PR Checklist

• Development: Related: Code Quality: Create details layout column generator #12505
• Approval: Have discussed with and got approval from the team¹
• Tests: Tested accessibility on the local end
• Deployment: Deployed the app on the local end
• Localization: Modified en-US string resources²
• Co-authors: N/A

Screenshots

Related codebase structure:

Footnotes

1. If the request hasn't been agreed by the team, this work might be rejected. Make sure that you get approval from the team before opening any PR related the request. ↩

2. If you removed any en-US string resources, make sure that there are no references of those resources. When you add a new en-US string resources, do not make any changes on other languages' resources; Crowdin will do that, instead. ↩

[yaira2]

Looks good behavior wise. I'd like to wait for an additional review from @gave92 or @hishitetsu before merging.

[hishitetsu]

Great work! LGTM

[hishitetsu]

GetHashCode() can be improved in the same way as LayoutPreferencesItem.

[0x5bfa]

Fixed already in the stage 2 PR. Thanks!