Update architecture section

[prrao87]

Summary

Rewrote the page as a compact architecture narrative for a technical buyer audience. It now opens directly with 2 to 3 paragraphs that explain what LanceDB Enterprise is, why the architecture exists, and how control plane, data plane, remote tables, and object storage fit together. Also replaces the old high-level architecture diagram with two mermaid diagrams that show more detail in the different system components.

Implementation Changes

Structure and flow

Used a tighter structure with a small number of sections:

• Opening prose with no subheader
• ## Compute-storage separation
• ## Architecture
• ## Remote tables
• ## Read path
• ## Write path
• ## Background work
• ## What this means for users

Public Interfaces / Vocabulary Changes

Docs vocabulary is updated to standardize on this page:

• control plane for governance, configuration, identity, and lifecycle management
• data plane for serving queries, reads/writes, and maintenance execution
• remote table for the user-facing abstraction over networked, storage-backed tables
• query nodes, plan executors, and indexers as the main execution roles

How this was tested

• Carefully vetted with GPT 5.4 and the latest Enterprise code base - code is the source of truth for grounding the explanations
• Validated that the Mermaid diagrams renders well locally.
• Read through the explanations for flow, clarity and conciseness, while still carrying enough detail to understand the working components.
• Check that any numbered flows are short and accurate, and that bullets are used sparingly.

Goals

• The rewrite (hopefully) feels more compelling through clarity and consequences, not through aggressive comparison language.
• The architecture page is meant to be mostly standalone and should not duplicate the explicit OSS comparison already present in the Enterprise overview.
• Namespace and catalog details are mentioned only lightly, enough to explain logical name resolution without turning this page into a catalog guide.