[codex] Fix config update path persistence

[wcole1-godaddy]

Summary

Fixes config update operations so they write back to the exact config file path that was resolved for the update. This prevents godaddy application add action from returning success while leaving the intended OTE TOML unchanged when a specific config path or environment-specific fallback is involved.

Root Cause

addActionToConfigEffect, addSubscriptionToConfigEffect, and addExtensionToConfigEffect resolved a target path, but then discarded that path and wrote through environment-based lookup again. Absolute config paths were also being joined onto process.cwd(), producing invalid duplicated paths in internal callers/tests.

Changes

• Preserve absolute config paths in getConfigFilePath.
• Reuse config path resolution for both Effect and sync config reads.
• Add a path-based config writer for update flows.
• Update action, subscription, and extension config mutations to write to the resolved path.
• Add a regression test proving action updates persist to an explicit OTE config file without creating/updating the wrong default file.

Validation

• pnpm exec tsc --noEmit
• pnpm run build
• pnpm test tests/unit/services/config-routing.test.ts
• pnpm test tests/integration/cli-smoke.test.ts tests/unit/application-deploy-security.test.ts tests/unit/cli/deploy-stream.test.ts
• rg "export async function" src
• rg "toEffect|effect-interop" src
• git diff --check