Generated SDK omits multipart/form-data operations (Cloudmersive Document Conversion, DocuWare)

## Summary

The `CodefulSdkGenerator` (`--directClient --language=typescript`) omits connector operations that declare `multipart/form-data`, because `ConnectorClientBase` cannot compose multipart request payloads. This surfaced during the Phase 3 & 4 connector rollout (#78).

## Impact

In the committed swagger snapshots:

- **Cloudmersive Document Conversion (`cloudmersiveconvert`)** — 67 of 128 operations declare `multipart/form-data` and are therefore not exposed on the generated client.
- **DocuWare (`docuware`)** — 5 of 21 operations, including `DeleteFile`.

These actions cannot currently be invoked through the generated SDK.

## Proposed fix

Add multipart request composition to `ConnectorClientBase` (or a dedicated multipart helper) and update the generator to emit the previously-omitted routes. This requires coordinated changes in the AzureUX-BPM `CodefulSdkGenerator` and the runtime base class, plus regeneration of the affected connectors.

## References

- PR #78 (Phase 3 & 4 SDK expansion) — reviewer note "Multipart/form-data operations are intentionally omitted".

Start by locating CodefulSdkGenerator and ConnectorClientBase, then trace how multipart/form-data operations are currently filtered from generated clients. Review the committed cloudmersiveconvert and docuware swagger snapshots and PR #78's multipart note. Done means the affected routes are generated and multipart requests can be invoked through the runtime SDK.

Written by the indexing model from the issue text.