destination-typesense: State message does not contain id error with Airbyte 1.7+

## Description

The destination-typesense connector fails with "State message does not contain id" errors when used with:
- CDC sources (e.g., Snowflake CDC)
- Airbyte platform 1.7+ which injects `state-id` tracking metadata into state messages

## Steps to Reproduce

1. Set up a CDC source (e.g., Snowflake) with destination-typesense
2. Run a sync
3. Data syncs successfully but the job is marked as "failed"

## Error Message

```
State message does not contain id
```

## Root Cause

The destination-typesense connector uses an older version of `airbyte-cdk` (`^6`) which drops unknown fields during state message serialization. When Airbyte 1.7+ injects `state-id` tracking metadata into state messages, this metadata gets stripped by the older CDK, causing the platform to fail the job.

The newer CDK (6.61.6+) properly preserves extra fields using `extra='allow'` semantics in the `AirbyteStateBlob` dataclass model.

## Environment

- Airbyte Platform: 1.7+
- Connector: destination-typesense v0.1.52
- Source: Any CDC source (Snowflake, Postgres CDC, etc.)

## Related

- #55697 (Databases CDC not working with Python CDK Destination Connectors)

## Fix

This issue is fixed by #70420 which upgrades the CDK to `>=6.61.6,<7.0`.