Restore unindented changelog continuation lines

The repo's agent instructions, updated in #211, now explicitly codify the
changelog style: 'wrapped entry text remains unindented rather than being
aligned beneath the bullet.'

My earlier commit e1db0f4 indented these continuations after surveying
existing entries (105 of 105 wrapped bullets were indented). That survey
measured the legacy style; the documented convention is a deliberate
forward-looking change, and andystaples had said as much in review. The
maintainer's stated preference is now written policy, so this reverts to
unindented.

Content is unchanged apart from removing 18 leading spaces.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: b6ec6f9e-f919-4874-b146-fa764b5c5617

Author: Bernd Verst

CHANGELOG.md

@@ -14,15 +14,15 @@ ADDED
 CHANGED
 
 - Importing `durabletask` no longer eagerly imports the worker implementation and its
-  dependencies (gRPC, protobuf, entities, serialization, OpenTelemetry). The public names
-  re-exported from the package — `ActivityWorkItemFilter`, `ConcurrencyOptions`,
-  `EntityWorkItemFilter`, `GrpcChannelOptions`, `GrpcRetryPolicyOptions`,
-  `LargePayloadStorageOptions`, `OrchestrationWorkItemFilter`, `PayloadStore`,
-  `VersioningOptions`, and `WorkItemFilters` — are now resolved on first use, so
-  `import durabletask` is substantially faster and loads far fewer modules. This
-  measurably reduces cold-start time for client-only applications, including those using
-  `durabletask.azuremanaged`, which shares the same `durabletask` namespace. All existing
-  import paths, `__all__`, `dir()`, and star-imports behave exactly as before.
+dependencies (gRPC, protobuf, entities, serialization, OpenTelemetry). The public names
+re-exported from the package — `ActivityWorkItemFilter`, `ConcurrencyOptions`,
+`EntityWorkItemFilter`, `GrpcChannelOptions`, `GrpcRetryPolicyOptions`,
+`LargePayloadStorageOptions`, `OrchestrationWorkItemFilter`, `PayloadStore`,
+`VersioningOptions`, and `WorkItemFilters` — are now resolved on first use, so
+`import durabletask` is substantially faster and loads far fewer modules. This
+measurably reduces cold-start time for client-only applications, including those using
+`durabletask.azuremanaged`, which shares the same `durabletask` namespace. All existing
+import paths, `__all__`, `dir()`, and star-imports behave exactly as before.
 - **Breaking:** `FailureDetails.error_type` — and the `errorType` value sent over the wire — is now the fully-qualified type name (`module.ClassName`, e.g. `builtins.ValueError`, `durabletask.task.TaskFailedError`) instead of the bare class name, matching the .NET and Java SDKs. Code that compared `error_type` against a bare name (for example `== "ValueError"`) must be updated to the qualified name or, preferably, switched to `FailureDetails.is_caused_by()`. Because this value is persisted and crosses the orchestration boundary, failures produced by older workers may still carry a bare name; `is_caused_by()` accepts both.
 
 ## v1.8.0