Fix Very Vanilla MQ path validation

[Teichoui]

Summary

Fixes Very Vanilla MQ path validation so relative packaged defaults are allowed, while absolute paths that point under an EverQuest folder containing eqgame.exe still hard-error clearly.

Why

RedFetch needs the MacroQuest folder, not an EverQuest executable path. This preserves bundled relative special-resource defaults while still catching user-selected invalid absolute MQ paths early.

Details

• Only runs eqgame.exe parent validation for absolute special-resource paths.
• Adds tests for relative defaults and absolute invalid Very Vanilla MQ paths.

Validation

• uv run --with pytest pytest tests/test_config_validation.py
• uv run --with pytest --with pytest-mock pytest
• python -m compileall -q src tests
• git diff --check origin/main...HEAD

Related to #22

[brainiac]

I'm confused why a path being relative somehow makes it OK to have eqgame.exe in its path.

The association between relative and absolute pathes and the safety of having eqgame.exe in a particular location isn't documented, if there is any at all.

This reads more to me like the path that has eqgame.exe in it happens to be a relative path.

What if EQ is on the desktop and MQ is installed inside of it and its a relative path?

[brainiac]

RedFetch needs the MacroQuest folder, not an EverQuest executable path. This preserves bundled relative special-resource defaults while still catching user-selected invalid absolute MQ paths early.

I read this like 5 times and still don't understand what this means. Can you explain it to me?