Use pytest fixtures for temporary paths to fix cwd dependency in fre make tests

[ceblanton]

Make YAMLPATH absolute, replace getcwd with tmp_path, use session tmp for interdependent tests. Resolves issue #738.

Describe your changes

Asked copilot to fix #738 using pytest fixtures to ensure a temporary directory is always available.

Issue ticket number and link (if applicable)

#738

Checklist before requesting a review

• I ran my code
• I tried to make my code readable
• I tried to comment my code
• I wrote a new test, if applicable
• I wrote new instructions/documentation, if applicable
• I ran pytest and inspected it's output
• I ran pylint and attempted to implement some of it's feedback
• No print statements; all user-facing info uses logging module

Note: If you are a code maintainer updating the tag or releasing a new fre-cli version, please use the release_procedure.md template. To quickly use this template, open a new pull request, choose your branch, and add ?template=release_procedure.md to the end of the url.

[ilaflott]

using relative pathing is almost as bad as using the current working directory.

try using site.getsitepackages()

[ceblanton]

using relative pathing is almost as bad as using the current working directory.

try using site.getsitepackages()

I don't understand.. this PR uses relative path from the pytest file, not relative path of the user.

I really think this pytest tmpdir fixture is the most recommended way to manage pytest work directories.

[ilaflott]

using relative pathing is almost as bad as using the current working directory.
try using site.getsitepackages()

I don't understand.. this PR uses relative path from the pytest file, not relative path of the user.

fair enough

I really think this pytest tmpdir fixture is the most recommended way to manage pytest work directories.

pytest fixtures for tmpdir == good idea always

[ceblanton]

closing in favor of #808