[Meilisearch v1.51.0] Add filter condition to Dynamic Search Rules

Context

Meilisearch v1.51.0 introduces filter conditions for Dynamic Search Rules (DSR). It also introduces a new lastUpdatedAt field in DSR responses.

Objective

Update the SDK to support:

• The new filter activation condition in the conditions object of a DSR. The filter condition contains a values key whose value is a JSON object mapping facet names to their expected filter values.
• The new lastUpdatedAt field returned by GET /dynamic-search-rules/{:ruleUid} and POST /dynamic-search-rules.

Use these resources:

• Release notes
• Search Rules Overview
  — API reference

Example of a DSR with a filter condition

// PATCH /dynamic-search-rules/test-filter
{
  "conditions": {
    "filter": {
      "values": {
        "color": "red",
        "category": "shirt"
      }
    }
  },
  "actions": [
    {
      "selector": {
        "indexUid": "products",
        "id": "123"
      },
      "action": { "type": "pin", "position": 1 }
    }
  ]
}

Tasks

• Update the conditions parameter to accept the new filter condition type
• Add the lastUpdatedAt field (ISO datetime string) to the API response shape
• Add tests for:
  • Creating/updating a DSR with a filter condition
  • Reading a DSR response containing lastUpdatedAt

Start by locating the SDK definitions for dynamic search rule conditions and response objects, then find the existing tests for creating, updating, and reading DSRs. Add coverage for the filter condition and lastUpdatedAt response field, and run the relevant test suite to verify both cases.