Is your feature request related to a problem? Please describe.

Flow Launcher currently requires absolute paths to execute binaries such as Python and Node.js. This creates issues when using the portable version, since paths change depending on where Flow Launcher is extracted or moved.
As a result, it is not possible to fully use Flow Launcher in a portable way with embedded runtimes, limiting its usability in portable setups, restricted corporate environments, or isolated systems.

Describe the solution you'd like

I would like Flow Launcher to support relative paths, allowing:

• Executables to be defined using paths relative to the Flow Launcher root directory
• Running embedded Python and Node.js runtimes directly from the portable folder