Moving Datastore Lake locations

The legacy in-process Lake move command has been removed. A Datastore binding owns its persisted canonical namespace, and runtime opens verify it against Effective configuration.

Changing an Application document does not move existing data. Treat a physical move as a reviewed deployment migration: quiesce writers, copy and verify data with infrastructure-owned tools, establish a new immutable binding or Datastore, and update configuration only after the authoritative state agrees. Runtime code never accepts a caller-selected source or destination path.