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.

Start at src/open-api/types.ts:156 and compare readTimeOut with the correctly typed connectionTimeOut field at the preceding line. Change the declaration so numeric millisecond values are accepted, then verify the TypeScript checks pass and that the public type matches the server's Integer field.

Written by the indexing model from the issue text.