Add ViewStore.binding migration examples to guide

Sources/ComposableArchitecture/Documentation.docc/Articles/MigrationGuides/MigratingTo1.7.md

@@ -721,6 +721,53 @@ TabView(selection: $store.tab.sending(\.tabChanged)) {
 }
 ```
 
+If the binding depends on more complex business logic, you can define a custom `get`-`set` property
+(or subscript, if this logic depends on external state) on the store to incorporate this logic. For
+example:
+
+@Row {
+  @Column {
+    ```swift
+    // Before
+
+    // In the view:
+    ForEach(Flag.allCases) { flag in
+      Toggle(
+        flag.description,
+        isOn: viewStore.binding(
+          get: { store.featureFlags.contains(flag) }
+          send: { store.send(.toggleFeature(flag)) }
+        )
+      )
+    }
+    ```
+  }
+  @Column {
+    ```swift
+    // After
+
+    // In the file:
+    extension StoreOf<Feature> {
+      subscript(hasFeatureFlag flag: Flag) {
+        get { featureFlags.contains(flag) }
+        set { send(.toggleFeature(flag) }
+      }
+    }
+
+    // In the view:
+    ForEach(Flag.allCases) { flag in
+      Toggle(
+        flag.description,
+        isOn: $store[hasFeatureFlag: flag]
+      )
+    }
+    ```
+  }
+}
+
+> **Tip:** When possible, consider moving complex binding logic into the reducer so that it can be
+> more easily tested.
+
 ## Computed view state
 
 If you are using the `ViewState` pattern in your application, then you may be computing values