feat: Add OR logic support to user fetch API filters

[socksprox]

Summary

Added support for OR logic between filters in the user/fetch endpoint while maintaining full backward compatibility with existing API clients.

Features

• Each filter can now specify a 'logic' parameter ('and' or 'or')
• Defaults to 'and' when not specified (backward compatible)
• Enables complex queries like finding users in multiple groups
• Supports mixing AND/OR conditions in a single request

Examples

Find users in multiple groups (OR logic)

{
  "filter": [
    {
      "id": "group_id",
      "value": [1, 2, 3, 4],
      "logic": "or"
    }
  ]
}

Find users with high traffic OR expired accounts

{
  "filter": [
    {
      "id": "total_used",
      "value": "gt:107374182400"
    },
    {
      "id": "expired_at",
      "value": "lt:1706400000",
      "logic": "or"
    }
  ]
}

Backward compatible (legacy format still works)

{
  "filter": [
    {
      "id": "id",
      "value": "gt:13"
    },
    {
      "id": "total_used",
      "value": "gt:10737418240"
    }
  ]
}

Changes

• Modified applyFilters method in UserController.php to support optional logic parameter
• When logic is not specified, defaults to 'and' (preserves existing behavior)
• When logic: 'or' is specified, uses orWhere instead of where

Backward Compatibility

✅ All existing API calls continue to work without any changes
✅ Legacy frontends require no modifications
✅ Only new requests with explicit logic: 'or' will use OR logic

[socksprox]

@cedar2025 👀make sure not to forget my pull requests :)