File errors do not distinguish between the database and the keyfile

### 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:

Currently, on the database credentials screen, if a file cannot be read due to a File Provider issue, it is not easy to determine whether the problem stems from the key file or the database.

### Describe the solution you'd like:

It would be helpful to add a visual cue to indicate where the problem is coming from, either by highlighting the database URI in red or by highlighting the key file in red.

### Describe alternatives you've considered:

_No response_

### Additional context:

_No response_

Start at the Android database credentials screen and trace how file-read errors from the database URI and key file are surfaced. Determine how to identify which file caused the File Provider failure, then make the affected field visibly distinct and verify that errors for each file are distinguishable.

Written by the indexing model from the issue text.