Fix PyInstaller build failure due to incorrect import path in wallet.py

[Copilot]

The Windows executable build workflow failed because wallet.py used an absolute import (from trinity_wallet_py.gui.main_window) that broke when PyInstaller ran from within the trinity_wallet_py directory.

Changes

• wallet.py: Changed to relative import from gui.main_window
• Updated sys.path to add current directory instead of parent directory

# Before
sys.path.insert(0, os.path.dirname(os.path.dirname(os.path.abspath(__file__))))
from trinity_wallet_py.gui.main_window import TrinityWalletGUI

# After  
sys.path.insert(0, os.path.dirname(os.path.abspath(__file__)))
from gui.main_window import TrinityWalletGUI

The build script executes PyInstaller from within trinity_wallet_py/, so imports must be relative to that directory. All other modules already use correct relative imports (..core.wallet, ..utils.base58, etc.).

Original prompt

Reference: https://github.com/Action-Committee/Trinity_py/actions/runs/20665461000/job/59337105598 I want make this work

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.