[GSoC'24] Refactor: Consolidate media paths into a single variable

[SanjaySargam]

Purpose / Description

This PR introduces a refactor to consolidate the media paths into a single variable mediaPath for better code maintainability and clarity.

How Has This Been Tested?

Realme 9 ( Physical Device )

Checklist

Please, go through these checks before submitting the PR.

• You have a descriptive commit message with a short title (first line, max 50 chars).
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the Google Accessibility Scanner

[Arthur-Milchior]

I assume you tested it, and can still import deck with image and sound. That you can still edit images

I admit I'd be more confortable if I knew why we had two fields originally. I guess there must have been a reason, but I can't easily understand it.
In particular because the value of the path is sometime changed, and sometime reverted to its previous value. So I would fear this would create interaction. Except that I don't see how you could be dealing with image and sound simultaneously.

[Arthur-Milchior]

I think you can remove the "unified". It seems to indicate that it's the result of a unification. Which is true, that's what you're doing in this commit. But that's not something the developer that will read this code have to know.
So, just:

Path of the folder containing media used by AnkiDroid.

I would not list all the media, because technically, it can be anything else. It can be font, it can be css files, javascript libraries, and I'm sure some advanced users created decks with more esoteric data.

[Arthur-Milchior]

I'd appreciate if you could add parenthesis. I never know which is the priority order, and would prefer not to have to learn it by hearth to be sure the change is correct

[criticalAY]

I am ok with this if Sanjay wants to use it somewhere but this will go under major refactoring once I am done with all multimedia fragments most likely remove it and other multimedia field class and introduce a better way to handle it

[david-allison]

Cheers

Truthfully: I'd hope that this is used for a purpose, as we're aiming to remove IField etc...

But the code change is good and @criticalAY is happy