[Feature Request] Save/Save As for workspace

Relates to #1638

I find myself repeating the process of Exporting the current workspace a lot. It becomes a tedious chore when you start to update your API frequently during development.

- The process is lengthy - it requires you to click through several modals where you make repeated selections
- The file name sometimes requires editing - for example: I might want to remove the date portion.
- There is no direct key combo to invoke it - you need to open the Workspace settings first which in fact has its own combo, but it is an extra step.

I would love to see a traditional **Save/Save As** tandem of menu commands as in many other programs operating on documents, ie:

- Save would only pertain to the current workspace
- Save would retain the selected format and file location/name
- at first invocation, Save would be equivalent to Save As

This would allow me to first **Save As...** into my project directory, from where it would be version controlled, and then I'd just **Save** whenever I feel like the file deserves an update.

IMO this would make the app more friendly and usable.

User should still be able to Export - the settings used for Export should not interfere with Save though.

Review the existing workspace Export flow and Workspace settings entry point first; the issue identifies these as the current interaction points. Define how Save and Save As retain the format and file location/name while remaining independent of Export, then verify that first-use Save behaves like Save As and later saves target the current workspace.

Written by the indexing model from the issue text.