Bug: [FIX]: Fix error message while using generic filter



Fix error message while using generic filter 
diff --git a/crates/diesel_models/src/query/generics.rs b/crates/diesel_models/src/query/generics.rs
index e23f4026ccf..d5581932eae 100644
--- a/crates/diesel_models/src/query/generics.rs
+++ b/crates/diesel_models/src/query/generics.rs
@@ -441,7 +441,7 @@ where
 
     track_database_call::<T, _, _>(query.get_results_async(conn), DatabaseOperation::Filter)
         .await
-        .change_context(errors::DatabaseError::NotFound)
+        .change_context(errors::DatabaseError::Others)
         .attach_printable("Error filtering records by predicate")
 }
 

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD

## Description
<!-- Describe your changes in detail -->
This PR changes the way we raise error if something goes wrong with generic filter. Currently we throw not found error which is wrong.

This feature is hard to test on hosted environments, as this requires to make some db changes so that we can get error in generic filter.

### Additional Changes

- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables

<!--
Provide links to the files with corresponding changes.

Following are the paths where you can find config files:
1. `config`
2. `crates/router/src/configs`
3. `loadtest/config`
-->


## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.

If you don't have an issue, we'd recommend starting with one first so the PR
can focus on the implementation (unless it is an obvious bug or documentation fix
that will have little conversation).
-->
We will able able to log correct error messages

## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant screenshots)?
-->
Tested it with dropping `organization_id` column in refund table while trying to create refund.
According to current implementation, we are raising not found error which is incorrect because it is not displaying the right cause.
<img width="1637" alt="Screenshot 2025-04-29 at 4 24 40 PM" src="https://github.com/user-attachments/assets/940fda38-c6dc-46ae-b6e1-01aabd6c2a4f" />

Implementation in this PR fixes this bug.
<img width="1534" alt="Screenshot 2025-04-29 at 4 28 33 PM" src="https://github.com/user-attachments/assets/d8a61239-433c-4d17-bfb6-0ae2d81c9cdb" />


## Checklist
<!-- Put an `x` in the boxes that apply -->

- [x] I formatted the code `cargo +nightly fmt --all`
- [x] I addressed lints thrown by `cargo clippy`
- [x] I reviewed the submitted code
- [ ] I added unit tests for my changes where possible
