[Bug]: Specify relative path for config file override

[ablankz]

🐞 Describe the Bug

Currently, if you specify the override file as a relative path, it is based on the path it is running on.

🔍 Steps to Reproduce

Steps to reproduce the behavior:

1. Describe the file you want to override($HOME/test/override.yaml)
2. Specify override files by relative path(./override.yaml) on main config($HOME/test/bloader.yaml)
3. Move to another directory ($HOME/test2) and execute the following.

   bloader store ls -c $HOME/test/bloader.yaml

🤔 Expected Behavior

$HOME/test/override.yaml should be specified, but $HOME/test2/override.yaml is searched and an error occurs.

📋 Additional Context

🌍 Environment

• OS: All
• Go version: 1.23
• CLI version: v1.0.0

[ablankz]

The same is true for all paths that can be specified in config and all paths other than the flow file specified in loader, regardless of the override of config.