MantisBT does not consistently evaluate stored_query_use_threshold in the requested project context. If a project-specific value permits a user to use saved filters while the global value is higher, the filters API incorrectly returns no filters.

Steps to reproduce

1. Create two projects.
2. Create a Reporter-level user with access to one project.
3. Set the global stored_query_use_threshold value to Developer.
4. Set the selected project’s stored_query_use_threshold value to Reporter.
5. Create a public named filter associated with that project.
6. Authenticate as the Reporter-level user and request GET /api/rest/filters?project_id=.
7. Observe that no filters are returned.

Expected result
The project’s public named filter is returned because the project-specific stored_query_use_threshold permits Reporter-level access.

For ALL_PROJECTS, filters should only be returned from accessible projects whose effective stored_query_use_threshold permits access, together with global filters.