[BUG] Transfer paths must be absolute doesn't propegate back to `pull file`

[sdelliot]

Bug Report

Description

When a user specifies a file to be extracted from a VM via the pull file helper, it may be possible that they do not input a complete path (e.g., firewheel pull file test.pcap server-0 /tmp). However, the vm_resource_handler.py will report the following error in the VM resource logs:

[2025-09-24 13:57:15 GMT ERROR] Transfer paths must be absolute! Cannot transfer: test.pcap
Traceback (most recent call last):
  File "/opt/firewheel/fwpy/lib/python3.10/site-packages/firewheel/vm_resource_manager/vm_resource_handler.py", line 621, in transfer_data
    self._transfer_data(name, location, interval, destination)
  File "/opt/firewheel/fwpy/lib/python3.10/site-packages/firewheel/vm_resource_manager/vm_resource_handler.py", line 659, in _transfer_data
    raise RuntimeError(
RuntimeError: Transfer paths must be absolute! Cannot transfer: test.pcap

Despite this error in the logs, the user will continue to see:

Checking if the file is ready... / 0:01:54

Steps to Reproduce

1. Create a file on a VM in the home directory /home/ubuntu/test.pcap (using tests.vm_gen:1)
2. From the control node run: firewheel pull file test.pcap server-0 /tmp

Expected Behavior

The error should be propagated from the VM resource logs back to the user so that the can correct their command.

Actual Behavior

Rather the error shows up in the logs and the helper continues to "spin" until manually killed by the user.

Environment

• Operating System: Ubuntu
• Version: 2.9.0
• Any Model Components Impacted: all

Checklist

• I have included no proprietary/sensitive information in my issue.