Optimizing Model Filter Get Method

[souvikinator]

Description

This PR fixes #

Notes for Reviewers
Before:

• In non-trim mode, when Components or Relationships was set to true in the ModelFilter, the system made N separate database calls (one per model).

After:

• Now, if Components or Relationships is enabled in the ModelFilter, the function executes a single bulk query for all models, one query for components and one query for relationships regardless of the number of models.

Signed commits

• Yes, I signed my commits.

[leecalcote]

Please review - https://github.com/meshery/meshkit/actions/runs/13452392615/job/37589077129?pr=687#step:4:56

[leecalcote]

Will you please describe where this function is being used and how this bulk behavior improves performance?

[souvikinator]

Yes, I'll do benchmarking and share it here.

[leecalcote]

Yes, I'll do benchmarking and share it here.

@souvikinator that's not what I'm asking for.

What other parts of Meshery use this functionality? How have you confirmed that you've not broken those areas with this change?

What is driving this change? Is there an open issue describing this or calling for this PR?

[souvikinator]

@leecalcote
There is no open issue or this was not pointed out specifically. While I was exploring the current search logic for the registry model tab I noticed optimization opportunity and proceeded with it.

I went through all the occurrences of this h.registryManager.GetEntities with ModelFilter.
Found these endpoints using it:
GET /api/meshmodels/models
GET /api/meshmodels/models/{model}
GET /api/meshmodels/export
GET /api/meshmodels/categories/{category}/models

Went to each part in the dashboard where these are being called and compared it to the playground in the production.