Add `temp-env` as a dev dependency and refactor tests (#4)
## Summary
- Introduce `temp-env` crate (v0.3) to simplify environment variable
handling in tests.
- Replace custom `env::set_var`/`env::remove_var` calls with `temp_env`
utility methods.
- Eliminate unsafe code in test cases by leveraging `temp_env`'s scoped
modification functions.
- Update `Cargo.toml` and `Cargo.lock` to reflect the new development
dependency.
## Type of Change
<!-- Mark with an `x` all that apply -->
- [ ] 🐛 Bug fix (non-breaking change that fixes an issue)
- [ ] ✨ New feature (non-breaking change that adds functionality)
- [ ] 💥 Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] 📚 Documentation update
- [x] 🧹 Code cleanup or refactoring
- [x] 🔧 Build system or dependency changes
- [x] 🧪 Test improvements
## What Changed?
This refactors tests to use temp-env instead of using unsafe code
## How Has This Been Tested?
<!-- Describe the tests you ran to verify your changes -->
- [x] Existing tests pass (`mise test`)
- [x] New tests added for new functionality
- [x] Manual testing performed
- [x] Code follows style guidelines (`mise lint`)
authored by
aaronmallen.dev
and committed by