fix(auth): normalize filter request and apply status filtering during bulk delete

[Tyagiquamar]

Closes #7020

Problem

When DELETE /orchestrator/user/bulk (and DELETE /orchestrator/role-group/bulk) was executed with a listingRequest filter (e.g. {"listingRequest":{"searchKey":"","status":["inactive"]}}), getUserIdsHonoringFilters and getGroupIdsHonoringFilters invoked the query builder without running default request normalization (SetDefaultValuesIfNotPresent) or setting status filter types (setStatusFilterType, setCurrentTimeInUserInfo). As a result, status filters were not applied and unbounded default scans could target all users instead of the filtered subset. Additionally, if the filter resolved to 0 IDs, the delete routines did not early-exit.

Solution

1. In getUserIdsHonoringFilters (pkg/auth/user/UserService.go), invoked SetDefaultValuesIfNotPresent, setStatusFilterType, and setCurrentTimeInUserInfo before building the query.
2. In getGroupIdsHonoringFilters (pkg/auth/user/RoleGroupService.go), invoked SetDefaultValuesIfNotPresent before building the query.
3. Added early return guards in BulkDeleteUsers and BulkDeleteRoleGroups when resolved request.Ids is empty.
4. Added unit tests for query building with search, pagination, and count checks in pkg/auth/user/repository/helper/UserRepositoryQueryBuilder_test.go.

[bito-code-review]

Bito Review Skipped - Source Branch Not Found

Bito didn't review this change because the pull request is no longer valid. It may have been merged, or the source/target branch may no longer exist.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud