Fix issue 2962

[priyatanu]

Pull request (PR) checklist

Please check if your pull request fulfills the following requirements:

• I've read the Contribution Guidelines and my PR doesn't break the rules.
• I've read and understand the Developer Guidelines.
• I confirm that I've run the code locally and everything works as expected.
• My PR includes only the necessary changes to fix the issue (i.e., no unnecessary files or lines of code are changed).
• 🎬 I've attached a screen recording of using the new code to the next paragraph (if applicable).

Screen recording of your changes (if applicable):

What's changed?

Describe with a few bullets what's new:
-I've fixed technical debt from the code

• Transitioned from direct CategoryDao and WriteCategoryDao interactions to using the repository

Before	After
{media}	{media}
{media}	{media}

Risk factors

What may go wrong if we merge your PR?

• No cases
• ...

In what cases won't your code work?

• It works for settings screen
• ...

Does this PR close any GitHub issues? (do not delete)

• Closes [Data Layer] Migrate the code to use the new the CategoryRepository #2962

Troubleshooting GitHub Actions (CI) failures ❌

Pull request checks failing? Read our CI Troubleshooting guide.

[priyatanu]

az_recorder_20240905_181705.mp4

[ILIYANGERMANOV]

@priyatanu a few notes:

1. Let's not update the CategoryRepo usages in the backup usacase because it seems too dangerous
2. Let's update CategoryDao -> CategoryRepo on all other places in the app

[ILIYANGERMANOV]

This will crash the app! We don't want such behavior

[priyatanu]

done. reverted

[Vishwa-Raghavendra]

@priyatanu a few notes:

1. Let's not update the CategoryRepo usages in the backup usacase because it seems too dangerous
2. Let's update CategoryDao -> CategoryRepo on all other places in the app

Also the dao layer deals with entity classes while repo layer deals with domain classes
old backups will start failing