Brief summary of issue / Description of requested feature:

During a Discord discussion on the #mudlet-testing channel it was suggested that the package export should indeed remember where packages were saved so that repeated exports could all sent to the same location more quickly.

Steps to reproduce the issue / Reasons for adding feature:

1. Using the PR BugFix: allow packages with sub-directories & get exporter to report result #2554 or the main code once that has been merged export a package, noting that the user has to specify where to put the finished object and that the destination directory selection always starts in the same place (prior to that PR it was the user's home directory, after that either the main Mudlet one or the one of the profile - I can't remember precisely which at this point). Chose a different location and proceed to generate the package.

2. Using the same code attempt to export a second package.

Error output / Expected result of feature

The second usage will not start where the previous use had put the package - the directory selection will start back at the same start point as the previous usage.

Extra information, such as Mudlet version, operating system and ideas for how to solve / implement: