Document exact-second UTC timestamp filtering for contacts search on 2.17

[adisan19]

Why?

In API version 2.17, contacts search filters standard timestamp fields on the exact UTC second and accepts !=, >= and <= on them, and Date custom attributes match by UTC calendar day. The 2.17 reference still describes the 2.16 behaviour of whole-day matching in the workspace timezone.

How?

Copies the Preview wording added in the PR below into the 2.17 search contacts description and the search operator description, for this change only.

• Document exact-second timestamp filtering for contacts search on Preview #627
• Companion: https://github.com/intercom/developer-docs/pull/1246

_{Generated with Claude Code}

[geetikabagga]

One gap: datetime is missing from the Data Attributes data_type enum. Everything else matches Preview.

• Preview #627 has five hunks. This PR copies four of them: the three in the search description and the operator schema line, each identical to descriptions/0. The fifth adds - datetime to components.schemas.data_attribute.data_type.enum, and 2.17 still lists only string, integer, float, boolean, date.
• 2.17 does return that value. GetDataAttributes only maps the standard timestamps back to date when ContactSearchDateUtcAnchor is inactive, and that change is in the 2.17 block. The new search text says so too ("These fields report a type of datetime on the Data Attributes endpoint"), and so does the 2.17 changelog. SDKs generated from this spec would reject datetime as an unknown enum value.
• One more difference from Preview is owner_id (Integer in Preview, String here). It's unrelated: it comes from #314, which predates this change. Leaving it as it is here is correct.

Add - datetime after - date in the data_attribute enum and this is good to go.

~ Automated via Claude

[adisan19]

Added - datetime to the data_attribute.data_type enum in ef077bf, matching Preview. Thanks!

~ Automated via Claude