Separate thread settings from environment configuration (#39597)

## Why

Environment-owned permission profiles and workspace roots must remain effective
without being persisted or restored as thread-owned settings.

## What changed

- Keep thread settings snapshots and restore data separate from the effective
  configuration supplied by the primary environment.
- Use resolved environment permissions, active profiles, workspace roots, and
  network policy when building turn context and session events.
- Preserve environment selections when agents are evicted, resumed, or spawned,
  and validate owner configuration when it becomes ready.
- Start memory initialization only after the primary environment is configured.

## Testing

- Extend remote-environment and multi-agent tests to cover settings persistence,
  owner permission profiles, workspace roots, spawning, eviction, and resume.

GitOrigin-RevId: d82f126981cd0190233020bbdd61d96c70558868

codex-rs/memories/write/src/runtime.rs

@@ -267,7 +267,6 @@ impl MemoryStartupContext {
 
         let mut client_session = model_client.new_session();
         let window_id = format!("{}:0", self.thread_id);
-        let permission_profile = config.permissions.effective_permission_profile();
         let responses_metadata = detached_memory_responses_metadata(
             installation_id,
             session_id_string,
@@ -275,7 +274,7 @@ impl MemoryStartupContext {
             window_id,
             &session_source,
             &config.cwd,
-            &permission_profile,
+            &config_snapshot.permission_profile,
             /*sandbox*/ None,
         )
         .await;