Feature Request: Simplified/Traditional Chinese Interoperability in Search

### Checks

- [x] I have read the Wiki, searched the open issues, and still think this is a new feature.

### Explain the problem clearly and succinctly:

Hi KeePassDX Team,
​I'm a regular user of your app. I would like to suggest an improvement for the Chinese search function.
​The Problem:
Currently, the search engine treats Simplified Chinese and Traditional Chinese as completely different characters. If I search in Simplified Chinese, I cannot find content written in Traditional Chinese, and vice versa. This limits the search results significantly.

### Describe the solution you'd like:

The Suggestion:
It would be great if the search feature could support Simplified/Traditional Chinese fallback or fuzzy matching. Ideally, a single query should retrieve results in both script variants.
Technical Note:
Many developers use open-source libraries like OpenCC (Open Chinese Convert) to map characters before indexing or searching to solve this easily.
This feature would greatly improve the experience for all Chinese-speaking users. Thanks for considering it!

### Describe alternatives you've considered:

_No response_

### Additional context:

_No response_

The issue does not name any files, tests, or search entry points. Start by locating the Android search implementation and determine where queries or indexed content are normalized; compare available Simplified/Traditional Chinese conversion options such as OpenCC. Done means a query in either script retrieves matching results in both variants, with tests covering the behavior.

Written by the indexing model from the issue text.