Add codespell support (config, workflow to detect/not fix) and make it fix some typos (#903)

More about codespell: https://github.com/codespell-project/codespell .

I personally introduced it to dozens if not hundreds of projects already
and so far only positive feedback.

CI workflow has 'permissions' set only to 'read' so also should be safe.

Let me know if just want to take typo fixes in and get rid of the CI

---------

Signed-off-by: Yaroslav O. Halchenko <debian@onerussian.com>

codex-rs/README.md

@@ -10,7 +10,7 @@ To that end, we are moving forward with a Rust implementation of Codex CLI conta
 - Can make direct, native calls to [seccomp](https://man7.org/linux/man-pages/man2/seccomp.2.html) and [landlock](https://man7.org/linux/man-pages/man7/landlock.7.html) in order to support sandboxing on Linux.
 - No runtime garbage collection, resulting in lower memory consumption and better, more predictable performance.
 
-Currently, the Rust implementation is materially behind the TypeScript implementation in functionality, so continue to use the TypeScript implmentation for the time being. We will publish native executables via GitHub Releases as soon as we feel the Rust version is usable.
+Currently, the Rust implementation is materially behind the TypeScript implementation in functionality, so continue to use the TypeScript implementation for the time being. We will publish native executables via GitHub Releases as soon as we feel the Rust version is usable.
 
 ## Code Organization
 

codex-rs/core/src/codex.rs

@@ -832,7 +832,7 @@ async fn run_turn(
         let prev_id = if store {
             state.previous_response_id.clone()
         } else {
-            // When using ZDR, the Reponses API may send previous_response_id
+            // When using ZDR, the Responses API may send previous_response_id
             // back, but trying to use it results in a 400.
             None
         };

codex-rs/core/src/exec.rs

@@ -318,7 +318,7 @@ pub(crate) async fn spawn_child_async(
     cmd.kill_on_drop(true).spawn()
 }
 
-/// Alternative verison of `spawn_child_async()` that returns
+/// Alternative version of `spawn_child_async()` that returns
 /// `std::process::Child` instead of `tokio::process::Child`. This is useful for
 /// spawning a child process in a thread that is not running a Tokio runtime.
 pub fn spawn_child_sync(

codex-rs/execpolicy/src/arg_resolver.rs

@@ -30,7 +30,7 @@ pub fn resolve_observed_args_with_patterns(
     // `suffix_patterns` and use that to determine how many args are left to
     // be matched by `vararg_pattern` (which could be zero).
     //
-    // After assocating positional args with `vararg_pattern`, we match the
+    // After associating positional args with `vararg_pattern`, we match the
     // `suffix_patterns` with the remaining args.
     let ParitionedArgs {
         num_prefix_args,

codex-rs/execpolicy/src/default.policy

@@ -136,7 +136,7 @@ define_program(
         ["--glob", "src"],
     ],
     # TODO(mbolin): Perhaps we need a way to indicate that we expect `rg` to be
-    # bundled with the host environment and we should be using that verison.
+    # bundled with the host environment and we should be using that version.
     system_path=[],
 )