Remove 600 project filtering limit from group dependency list

What does this MR do and why?

We disable filtering on the dependency list if there are more than 600 projects in the group hierarchy. This MR removes the limit.

This limit was instated before we completed Group-level dependency list page performance im... (&12371 - closed). After these improvements, this limit is no longer necessary because we no longer have to traverse the entire hierarchy of the group. Group size no longer causes the query performance to degrade.

Query Analysis

• Project filter dropdown (no search): 50 ms https://console.postgres.ai/gitlab/gitlab-production-main/sessions/38996/commands/119875
• Project filter dropdown (short query): 58 ms https://console.postgres.ai/gitlab/gitlab-production-main/sessions/37188/commands/113874
• Component name dropdown (short query): 2.6 s https://console.postgres.ai/gitlab/gitlab-production-main/sessions/37188/commands/113875

References

• Group-level dependency list page performance im... (&12371 - closed)
• Consider removing dependency list project limit (#521942 - closed)
• Optimize searching projects with component version (!189803 - merged)
• Discussion where this limit was introduced: #411257 (comment 1508315283)

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.