Update reportIssue formatting to avoid console errors (#3795)

When a non-ASCII character is fed to `reportIssue`, the following is
output to the console:

```
<decode: bad range for [%@] got [offs:330 len:1073 within:0]>
```

This causes a lot of confusion for folks, so let's update the formatting
to avoid this.

Author: stephencelis

Sources/ComposableArchitecture/Core.swift

@@ -146,7 +146,7 @@ final class RootCore<Root: Reducer>: Core {
                 if isCompleted.value {
                   reportIssue(
                     """
-                    An action was sent from a completed effect:
+                    An action was sent from a completed effect.
 
                       Action:
                         \(debugCaseOutput(effectAction))

Sources/ComposableArchitecture/Dependencies/Dismiss.swift

@@ -123,7 +123,7 @@ public struct DismissEffect: Sendable {
     else {
       reportIssue(
         """
-        A reducer requested dismissal at "\(fileID):\(line)", but couldn't be dismissed. …
+        A reducer requested dismissal at "\(fileID):\(line)", but couldn't be dismissed.
 
         This is generally considered an application logic error, and can happen when a reducer \
         assumes it runs in a presentation context. If a reducer can run at both the root level \

Sources/ComposableArchitecture/Documentation.docc/Tutorials/BuildingSyncUps/08-RecordMeeting/ImplementingTimer-04-code-0007.swift

@@ -30,6 +30,6 @@ struct RecordMeetingTests {
     // ❌ The store received 1 unexpected action by the end of this test: …
     //
     //   Unhandled actions:
-    //     • .timerTick
+    //     .timerTick
   }
 }

Sources/ComposableArchitecture/Effect.swift

@@ -113,7 +113,7 @@ extension Effect {
               guard let handler else {
                 reportIssue(
                   """
-                  An "Effect.run" returned from "\(fileID):\(line)" threw an unhandled error. …
+                  An "Effect.run" returned from "\(fileID):\(line)" threw an unhandled error.
 
                   \(String(customDumping: error).indent(by: 4))
 

Sources/ComposableArchitecture/Effects/TaskResult.swift

@@ -271,7 +271,7 @@ extension TaskResult: Equatable where Success: Equatable {
               let lhsTypeName = typeName(lhsType)
               reportIssue(
                 """
-                "\(lhsTypeName)" is not equatable. …
+                "\(lhsTypeName)" is not equatable.
 
                 To test two values of this type, it must conform to the "Equatable" protocol. For \
                 example:
@@ -307,7 +307,7 @@ extension TaskResult: Hashable where Success: Hashable {
             let errorType = typeName(type(of: error))
             reportIssue(
               """
-              "\(errorType)" is not hashable. …
+              "\(errorType)" is not hashable.
 
               To hash a value of this type, it must conform to the "Hashable" protocol. For example:
 

Sources/ComposableArchitecture/Observation/Binding+Observation.swift

@@ -111,7 +111,7 @@ extension BindingAction {
         }
         reportIssue(
           """
-          A binding action sent from a store was not handled. …
+          A binding action sent from a store was not handled.
 
             Action:
               \(typeName(Action.self)).binding(.set(_, \(valueDump)))

Sources/ComposableArchitecture/Observation/NavigationStack+Observation.swift

@@ -389,7 +389,7 @@ public struct _NavigationLinkStoreContent<State, Label: View>: View {
               """
           reportIssue(
             """
-            A navigation link at "\(fileID):\(line)" is unpresentable. …
+            A navigation link at "\(fileID):\(line)" is not presentable.
 
               NavigationStack state element type:
                 \(elementType)

Sources/ComposableArchitecture/Observation/Store+Observation.swift

@@ -500,16 +500,16 @@ extension Store where State: ObservableState {
 
 func uncachedStoreWarning<State, Action>(_ store: Store<State, Action>) -> String {
   """
-  Scoping from uncached \(store) is not compatible with observation.
+  Scoping from uncached '\(store)' is not compatible with observation.
 
   This can happen for one of two reasons:
 
-  • A parent view scopes on a store using transform functions, which has been \
+  1. A parent view scopes on a store using transform functions, which has been \
   deprecated, instead of with key paths and case paths. Read the migration guide for 1.5 \
   to update these scopes: \
   https://swiftpackageindex.com/pointfreeco/swift-composable-architecture/main/documentation/composablearchitecture/migratingto1.5
 
-  • A parent feature is using deprecated navigation APIs, such as 'IfLetStore', \
+  2. A parent feature is using deprecated navigation APIs, such as 'IfLetStore', \
   'SwitchStore', 'ForEachStore', or any navigation view modifiers taking stores instead of \
   bindings. Read the migration guide for 1.7 to update those APIs: \
   https://swiftpackageindex.com/pointfreeco/swift-composable-architecture/main/documentation/composablearchitecture/migratingto1.7

Sources/ComposableArchitecture/Reducer/Reducers/ForEachReducer.swift

@@ -281,22 +281,22 @@ public struct _ForEachReducer<
     if state[keyPath: self.toElementsState][id: id] == nil {
       reportIssue(
         """
-        A "forEach" at "\(self.fileID):\(self.line)" received an action for a missing element. …
+        A "forEach" at "\(self.fileID):\(self.line)" received an action for a missing element.
 
           Action:
             \(debugCaseOutput(action))
 
         This is generally considered an application logic error, and can happen for a few reasons:
 
-        • A parent reducer removed an element with this ID before this reducer ran. This reducer \
+        A parent reducer removed an element with this ID before this reducer ran. This reducer \
         must run before any other reducer removes an element, which ensures that element reducers \
         can handle their actions while their state is still available.
 
-        • An in-flight effect emitted this action when state contained no element at this ID. \
+        An in-flight effect emitted this action when state contained no element at this ID. \
         While it may be perfectly reasonable to ignore this action, consider canceling the \
         associated effect before an element is removed, especially if it is a long-living effect.
 
-        • This action was sent to the store while its state contained no element at this ID. To \
+        This action was sent to the store while its state contained no element at this ID. To \
         fix this make sure that actions for this reducer can only be sent from a store when \
         its state contains an element at this id. In SwiftUI applications, use "ForEachStore".
         """,

Sources/ComposableArchitecture/Reducer/Reducers/IfCaseLetReducer.swift

@@ -215,7 +215,7 @@ public struct _IfCaseLetReducer<Parent: Reducer, Child: Reducer>: Reducer {
       reportIssue(
         """
         An "ifCaseLet" at "\(self.fileID):\(self.line)" received a child action when child state \
-        was set to a different case. …
+        was set to a different case.
 
           Action:
         \(String(customDumping: action).indent(by: 4))
@@ -224,16 +224,16 @@ public struct _IfCaseLetReducer<Parent: Reducer, Child: Reducer>: Reducer {
 
         This is generally considered an application logic error, and can happen for a few reasons:
 
-        • A parent reducer set "\(typeName(Parent.State.self))" to a different case before this \
+        A parent reducer set "\(typeName(Parent.State.self))" to a different case before this \
         reducer ran. This reducer must run before any other reducer sets child state to a \
         different case. This ensures that child reducers can handle their actions while their \
         state is still available.
 
-        • An in-flight effect emitted this action when child state was unavailable. While it may \
+        An in-flight effect emitted this action when child state was unavailable. While it may \
         be perfectly reasonable to ignore this action, consider canceling the associated effect \
         before child state changes to another case, especially if it is a long-living effect.
 
-        • This action was sent to the store while state was another case. Make sure that actions \
+        This action was sent to the store while state was another case. Make sure that actions \
         for this reducer can only be sent from a store when state is set to the appropriate \
         case. In SwiftUI applications, use "SwitchStore".
         """,