refactor: optimize group retrieval using query builder

[caleeli]

Issue & Reproduction Steps

There is a string query building in the code that can be improved.

Solution

• Use DB::table and whereIn to improve this query preparation.

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-33295

.

[cursor]

PR Summary

Low Risk
Equivalent SQL with safer binding via the query builder; no change to assignment rules or user filtering logic.

Overview
When resolving nested group members for task assignment, active subgroup IDs are now loaded with Laravel’s query builder (DB::table('groups')->whereIn()->where('status', 'ACTIVE')->pluck('id')) instead of hand-built ? placeholders and a raw DB::select on groups.

The loop still pushes only those active subgroup IDs onto the pending queue for further member expansion; this is a query-style cleanup in a process-execution hot path, not a behavior change.

^{Reviewed by Cursor Bugbot for commit b6fd1d9. Bugbot is set up for automated code reviews on this repo. Configure here.}

[decisions-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube