[Bug]: Running Tests Overwrites settings.toml Values

[CyanVoxel]

Checklist

• I am using an up-to-date version.
• I have read the documentation.
• I have searched existing issues.

TagStudio Version

Alpha 9.5.2 (main branch)

Operating System & Version

macOS 15.4.1

Description

Running the PyTest tests (specifically test_read_settings) overwrites the user's actual settings.toml file with values from the test.

Expected Behavior

Running tests should not affect the user's live files and should instead use mock files and directories for tests.

Steps to Reproduce

1. Ensure you have a TagStudio settings.toml file, perferably with non-default values
2. Run the PyTest tests, or at the very least the test_read_settings test
3. Observe the modified values

Logs

No response

[zfbx]

I feel like this could of been my fault, but you opened this 3 hours ago but only merged my changes 2 hours ago, was this test using the #903 code?

[CyanVoxel]

I feel like this could of been my fault, but you opened this 3 hours ago but only merged my changes 2 hours ago, was this test using the #903 code?

I tested it on main and had noticed my settings file getting reset occasionally beforehand, but didn't discover the reason until testing #903 - I'm not sure why that PR changed the behavior to write the values from the test instead of resetting it to the default values, but in either case it's undesirable behavior. My assumption is that no matter the temporary library directory being passed to the test, since it's the global settings file it'll always end up pointing to the user's settings.toml file in their system's config directory