docs: keep the stable-row-id caveat for deployments

The earlier change dropped every statement that a materialized view's
source needs stable row ids, because main no longer requires them. That
holds for the local SDK only. Sophon main creates a view through SQL by
default with the creation checks of its pinned lancedb (00f5dd6f), which
predates #4373 and still rejects a source without stable row ids.

The refresh and management pages now say a local view needs no special
source and a deployment may still require stable row ids, and the
architecture, limits, table and database pages note that requirement.
The summaries say a refresh brings a view up to date instead of saying
it recomputes it, since a deployment may reconcile changes rather than
rebuild.

docs/web/sql/ddl/materialized-view.mdx

@@ -13,8 +13,9 @@ A materialized view stores a query's result as rows, kept current by a refresh
 
 <Note>
 Materialized views are off by default on a deployment and have to be enabled
-there. Which statements and query shapes a deployment accepts, and how it
-refreshes a view, depend on its LanceDB Enterprise version and configuration.
+there. Which statements and query shapes a deployment accepts, whether it needs
+the source table to have stable row ids, and how it refreshes a view depend on
+its LanceDB Enterprise version and configuration.
 </Note>
 
 ## CREATE MATERIALIZED VIEW {#create}
@@ -67,6 +68,6 @@ as any table.
     Creating one from the SDK.
   </Card>
   <Card title="Refresh a materialized view" icon="arrows-rotate" href="/feature-engineering/materialized-views">
-    What a refresh recomputes, locally and on a deployment.
+    How a refresh works, locally and on a deployment.
   </Card>
 </CardGroup>