Draft: Add min_access_level filter to catalog resources query

What does this MR do and why?

This change adds a new filtering option called "minimum access level" to the catalog resources feature. When users browse the catalog of available resources, they can now filter to only see resources where they have a specific level of permission (like reporter, developer, maintainer, or owner access) on the underlying projects.

The implementation adds this filter as a new parameter that can be passed through the GraphQL API, and it works by checking the user's actual permissions on each project before including its resources in the results. This is useful for scenarios where users want to find only resources they can meaningfully contribute to or manage, rather than just view.

The change includes comprehensive test coverage to ensure the filtering works correctly at different permission levels and combines properly with existing filters like search and sorting.

References

Investigate `Your Groups` query to have a permi... (#583419) • Rajendra Kadam • 18.8

Screenshots or screen recordings

Before	After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.