Local configuration to define default "downloads"/transfer directory for transferred files

Is your feature request related to a problem? Please describe. When using t to transfer a file from a pod onto my local machine, my understanding is that the file always lands by default in the working directory I was in when I started k9s. I'd like to have a bit more control over where transferred files land on my local machine.

Describe the solution you'd like I'd like a configuration setting that allows users to define a default directory for transferred files to land in. I'm open to either the directory being pre-populated in the file transfer dialog box (like the pod currently is), or for the directory to be "hidden" in that dialog box with the user understanding that the "To" field will be appended to the configuration setting directory.

Describe alternatives you've considered I haven't considered many alternatives. The obvious alternative is just to type in the full destination path, but that's a bit tedious, which is why I'm looking for a solution. I'm very open to other, better ideas for how to accomplish the same goal. If there's a more k9s-y way to solve this, please let me know!

Additional context If creating a configuration setting is the right way to handle this, I can create a draft PR to implement it. I wanted to get feedback on this idea before doing that. Thank you!