Expose orchestration version in paged status results

Azure/azure-functions-durable-extension#3532 adds an optional Version property to DurableOrchestrationStatus and exposes it as version in HTTP status responses.

The SQL provider's paged query path manually constructs DurableOrchestrationStatus in src/DurableTask.SqlServer.AzureFunctions/SqlDurabilityProvider.cs (GetOrchestrationStateWithPagination) but does not copy OrchestrationState.Version. Consequently, single-instance status queries expose the version through the extension's shared conversion, while collection queries (GET /instances, Node/Python getStatusAll and getStatusBy) omit it for MSSQL.

After a compatible WebJobs Durable extension package containing the new property is available:

• Map s.Version into DurableOrchestrationStatus.Version, normalizing the unversioned empty-string sentinel consistently with the extension.
• Add coverage for versioned and unversioned paged query results.

Related extension PR: Azure/azure-functions-durable-extension#3532

Start in src/DurableTask.SqlServer.AzureFunctions/SqlDurabilityProvider.cs, focusing on GetOrchestrationStateWithPagination and how it constructs DurableOrchestrationStatus. Check the compatible WebJobs Durable extension package and compare its version handling with the shared conversion. Done means paged results cover both versioned and unversioned orchestration states.