HttpInputParameters.readTimeOut typed as string — server expects integer (ms)

## Summary

`HttpInputParameters.readTimeOut` is typed as `string` in `src/open-api/types.ts:156`.
The server's `HttpTask.Input.readTimeOut` is `Integer` (milliseconds). The sibling field
`connectionTimeOut` is correctly typed as `number`. The inconsistency is a bug.

## Server baseline

Conductor **3.32.0-rc.9**

## Evidence

**Static:**
```typescript
// src/open-api/types.ts:155-156
connectionTimeOut?: number; // ✓ correct
readTimeOut?: string; // ✗ should be number
```

**Server:**
```java
// http-task/.../HttpTask.java:275
private Integer readTimeOut = 3000;
```

**Live (2026-07-16):** Server accepts both `readTimeOut: 3000` (integer) and
`readTimeOut: "3000"` (string) due to Jackson coercion. However, the TypeScript type
is still wrong — passing a number for `readTimeOut` is a compile-time error with the
current type definition.

## Impact

TypeScript users who pass `readTimeOut: 5000` (the natural form) get a type error and
must write `readTimeOut: "5000"` (string), which is semantically confusing and diverges
from `connectionTimeOut: 5000` (number).

## Proposed fix

```typescript
// src/open-api/types.ts:156
readTimeOut?: number; // was: string
```

## Related

Discovered during systematic SDK audit against Conductor OSS 3.32.0-rc.9.

Beginne bei src/open-api/types.ts:156 und vergleiche readTimeOut mit dem korrekt typisierten Feld connectionTimeOut in der vorherigen Zeile. Ändere die Deklaration so, dass numerische Millisekundenwerte akzeptiert werden, und überprüfe anschließend, dass die TypeScript-Prüfungen erfolgreich sind und der öffentliche Typ mit dem Integer-Feld des Servers übereinstimmt.

Vom Indexierungsmodell aus dem Issue-Text verfasst.