Align paired sync/aio clients with Azure SDK contracts

[hallvictoria]

Description

Align all 99 generated connector clients with Azure SDK conventions while retaining paired synchronous root and asynchronous azure.connectors.aio surfaces. The final catalog is reproducible offline from 99 committed Swagger snapshots captured from live BTS4 managed connector metadata in westus, with generator and output hashes pinned in generation.manifest.json.

This revision resolves the remaining review findings across generated API shape, Azure Core paging and polling contracts, exception compatibility, statically discoverable package exports, required model fields, samples, and generation provenance.

Paired Generator PR

• No generator changes required
• Generator PR: https://msazure.visualstudio.com/One/_git/AzureUX-BPM/pullrequest/17490020
• Generator revision: d3bc32c1b5fd0781a317fbd16f93a082e362ee93

Changes

Generated clients

• Regenerate 99 sync and 99 aio connector modules from pinned Swagger snapshots.
• Add structured Args, Returns, and Raises documentation to every generated operation.
• Make optional operation parameters keyword-only and expose pageable operations through ItemPaged and AsyncItemPaged without public continuation controls.
• Infer omitted pageable item properties, follow continuation fields present in response schemas, and emit bounded collection envelopes as list_* pagers over their primary arrays.
• Preserve begin_* operations through LROPoller and AsyncLROPoller.
• Emit required dataclass fields as required constructor arguments and optional fields as keyword-only arguments while preserving wire names.
• Keep sync and aio clients on shared root-owned model classes.

SDK, provenance, and samples

• Preserve synchronous transport timeouts when explicit policy chains omit retry handling.
• Make ConnectorException derive from Azure Core HttpResponseError while retaining connector operation, status, and response-body context.
• Add lazy runtime exports plus root and aio type stubs so every generated client remains statically discoverable without eager imports.
• Add committed Swagger snapshots, an offline regeneration command, and a manifest that pins the compiler, generator revision, snapshot hashes, and output hashes.
• Update all paired sync/aio samples for generated method names, typed request models, and pager consumption.
• Refresh Azure SDK guideline, generation, and generated-contract documentation.

Tests

• Extend catalog contracts for paging, conditional headers, keyword-only signatures, sync/aio parity, LROs, model construction, exports, and provenance.
• Add focused coverage for Jira
  extPage` traversal and primary collection selection when bounded envelopes also contain auxiliary array metadata.
• Adapt connector-specific tests to the regenerated public surface.
• Add static and execution coverage for all regenerated samples.

Testing

• Unit tests added/updated
• All existing tests pass (pytest): 4,925 passed
• Linting passes (python -m flake8 --config .flake8 --extend-ignore=D)
• Manual testing (offline regeneration and catalog audits described below)

Additional validation:

• 849 CodefulSdkGenerator tests passed.
• Deterministic offline regeneration verified across all 99 connectors.
• All 198 sync/aio sample files pass API compatibility validation; 264 sample execution cases pass.
• Mypy passed for all SDK source files.
• git diff --check passed.

Checklist

• Code follows the project's coding conventions
• Generated connector files were produced by the paired generator revision
• Type hints added to all public API signatures
• Documentation updated
• CHANGELOG.md updated

[David Burg (daviburg)]

[Dobby] Connector SDK review: two medium-priority runtime defects reproduced on the current head; see the separate inline comments. The earlier constructor-timeout forwarding finding no longer reproduces after the latest SDK update, so it is not included as an open finding.