Force Realm to be built as a dynamic library when installing via SPM

This is required for compliance with the new privacy manifest rules. While App
Store Connect supports static libraries, Xcode doesn't actually build static
libraries for static targets; it just links the object files directly into the
app. It also doesn't implement the xcprivacy manifest merging that the
documentation claims exists, so our privacy manfiest is never actually used.

CHANGELOG.md

@@ -9,6 +9,9 @@ x.y.z Release notes (yyyy-MM-dd)
   ([Core #7552](https://github.com/realm/realm-core/pull/7552)).
 * Improve perfomance of IN queries and chained OR equality queries for
   UUID/ObjectId types. ([.Net * #3566](https://github.com/realm/realm-dotnet/issues/3566))
+* Force building as a dynamic library when installing via SPM. This is required
+  to work around Xcode building static targets in a way incompatible with App
+  Store Connect's privacy manifest scanning.
 
 ### Fixed
 * `-[RLMUser allSessions]` did not include sessions which were currently

Package.swift

@@ -147,6 +147,7 @@ let package = Package(
     products: [
         .library(
             name: "Realm",
+            type: .dynamic,
             targets: ["Realm"]),
         .library(
             name: "RealmSwift",