[Bug]: Cachy-update UX: don't ask the user for package sub-dependencies, use defaults

### Kernel

7.1.1-2

### Desktop Environment / Window Manager

KDE Plasma

### CPU

YES

### GPU / Driver

ALSO YES

### Description

cachy-update usually asks the user for what version of some random package sub-dependency I want to install.
For example, recently I got asked for ["tesseract-data" package](https://archlinux.org/groups/x86_64/tesseract-data/), and it showed me a list of around 50 packages, all with the same name plus a language suffix, by alphabetical order: "tesseract-data-afr", "tesseract-data-amh",...(many other options inbetween),... and "tesseract-data-eng" if you are lucky enough not to miss it and not to select the default option [0] that is for the afrikans language (haha LOL), if you don't pay attention and select the default, you will just get punished with a language that has nothing to do with the language selected in your system.

Maybe this part of the issue should be also reported to some other repo like Arch or the tesseract project, I honestly don't know, hopefully someone will point this out where it should be.
Imagine if every app started to ask you what language you want via cachy-update without even looking at your system language preferences.

However cachy-update is also responsible for the UX, not just this package, but in general, it should stop asking the user for package sub-dependencies that I have no idea wtf they even are or do.

Can you imagine going to a cafeteria to order a coffee and being asked what kind of screw I want them to use to fix the truck engine that brings the coffee beans to the cafeteria? and it is mandatory to answer, and if you fail choosing one, the system will likely fail in some cases.
Well, that sums what cachy-update does to you.
One thing is being able to choose, and another is to force me to make a choice and not having valid and proven default values. Also those questions block the update process, (at least by default in case someone comes with some command-line parameter that skips questions, that is too hidden too late).

### Steps to Reproduce

1. Try to migrate from Windows or Ubuntu to CachyOS.
2. Try to do some simple task like updating your system.
3. Hate life.
4. Be forced to become a Linux kernel programmer to learn how to run a simple update.
5. Enter the matrix.

### Expected Behavior

Expecting an updater to just update my software is probably out of scope,
and this will probably be flagged as a feature request instead of a bug and forever be forgotten,
so I don't know what I was expecting.

### Actual Behavior

-

### Logs / Error Messages

-

### Additional Context

_No response_

Start by reproducing the update flow through cachy-update and observe where package sub-dependency prompts block the process. Use the tesseract-data example to check the behavior. Done means a normal update uses defaults for such dependencies instead of requiring a user choice.

Written by the indexing model from the issue text.