Update Rust crate ignore to v0.4.24

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
ignore (source)	workspace.dependencies	patch	0.4.23 -> 0.4.24

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Fixes #21081

---

Release Notes

BurntSushi/ripgrep (ignore)

v0.4.24

Compare Source

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Diagnostic diff on typing conformance tests

No changes detected when running ty on typing conformance tests ✅

[github-actions]

mypy_primer results

No ecosystem changes detected ✅
No memory usage changes detected ✅

[github-actions]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

Formatter (stable)

✅ ecosystem check detected no format changes.

Formatter (preview)

✅ ecosystem check detected no format changes.

[MichaReiser]

@BurntSushi any suggestions on what we should change on the ruff/ty side as part of this update? I see from the commits that there's a new global cwd option. Is this something we have to or should set now?

[BurntSushi]

Yeah, the WalkBuilder::current_dir method lets you set the directory used for matching gitignore patterns from global gitignore exclusions or files added via WalkBuilder::add_ignore. If you don't set it, then it will automatically be pulled from std::env::current_dir for every use of WalkBuilder::build{_parallel}.

The main reasons to use WalkBuilder::current_dir explicitly are:

1. You have a slightly different way of discovering the current working directory.
2. You use many WalkBuilder::build{_parallel} calls but only want to query std::env::current_dir once.
3. You don't want your libraries inspecting process global state for $reasons.

If those don't apply to ruff, then I think you can just leave it.

[MichaReiser]

Thanks, that's helpful

2. applies for both ty and ruff (although I consider this more a nice to have rather than being very performance critical)
   1 and 3: Apply for ty where we want to sue OsSystem::current_directory over std::env::current_dir (they should be the same but for consistency's sake)