Make sure failures in multiline CI steps are not swallowed.

Without this change, it is possible to have a passing CI job even
though the build failed, e.g.

https://github.com/dabrahams/CBORCoding/actions/runs/6806944368/job/18509010389#step:4:99

Author: dabrahams

.github/workflows/carthage.yml

@@ -1,4 +1,7 @@
 name: Carthage
+defaults:
+  run:
+    shell: bash -eo pipefail {0}
 on:
   workflow_dispatch:
   push:

.github/workflows/cocoapods.yml

@@ -1,4 +1,7 @@
 name: Cocoapods
+defaults:
+  run:
+    shell: bash -eo pipefail {0}
 on:
   workflow_dispatch:
   push:

.github/workflows/documentation.yml

@@ -1,4 +1,7 @@
 name: Documentation
+defaults:
+  run:
+    shell: bash -eo pipefail {0}
 on:
   workflow_dispatch:
   push:

.github/workflows/publish-cocoapods.yml

@@ -1,4 +1,7 @@
 name: Publish CocoaPods
+defaults:
+  run:
+    shell: bash -eo pipefail {0}
 on:
   release:
     types: [published]

.github/workflows/swift-package.yml

@@ -1,4 +1,7 @@
 name: Swift Package
+defaults:
+  run:
+    shell: bash -eo pipefail {0}
 on:
   workflow_dispatch:
   push:

.github/workflows/swiftlint.yml

@@ -1,4 +1,7 @@
 name: SwiftLint
+defaults:
+  run:
+    shell: bash -eo pipefail {0}
 on:
   workflow_dispatch:
   push:

.github/workflows/upload-assets.yml

@@ -1,4 +1,7 @@
 name: Upload Assets
+defaults:
+  run:
+    shell: bash -eo pipefail {0}
 on:
   release:
     types: [published]

.github/workflows/xcframework.yml

@@ -1,4 +1,7 @@
 name: XCFramework
+defaults:
+  run:
+    shell: bash -eo pipefail {0}
 on:
   workflow_dispatch:
   push:

.github/workflows/xcodebuild.yml

@@ -1,4 +1,7 @@
 name: Xcode Project
+defaults:
+  run:
+    shell: bash -eo pipefail {0}
 on:
   workflow_dispatch:
   push: