Property filters and inline properties for object listing (API and MCP)

Listing objects by type returns only IDs, so reading Task status, date, deadline, or completed time requires one fetch per task. My space has ~525 tasks (~88 open). A full refresh takes ~100 calls, ~3.5 minutes, and hits rate limits, all to read values the server already stores.

Please add, in both the REST API and the MCP server:

1. Property filters on object listing: status (equals/in), date and deadline (before/on/after/between), and completed (between two ISO 8601 timestamps), combinable with AND and with tag/collection filters.

2. Selected properties returned inline in list results (for example properties=status,date,deadline,completed,tags), or a batch get by up to 100 IDs.

3. A modifiedSince/updatedAfter parameter on listing.

4. Sorting by property (deadline, completed, lastUpdated).

Example: "Tasks completed between 2026-10-28T04:00Z and 2026-10-29T04:00Z" or "Tasks not Done or Canceled with deadline on or before 2026-11-04" should each be one paginated call, with no per-object fetches.