Allow location choosing when saving as new asset

[yannkost]

We’ve received feedback from multiple clients that the “Save as new asset” behavior in the Image Editor is confusing. Users want to know where the new asset is saved and, ideally, see the target folder and resulting filename before saving.

In addition, when the Image Editor is opened from an asset field, it doesn’t appear to replace the current image by default. Replacement only seems to work reliably when the Image Editor is opened via the sidebar drawer.

Workflow gaps we currently can’t support
Creating a cropped version for an empty asset field
The client wants to create a crop of an existing asset directly into an empty asset field. Right now, they must first select an image, then open the Image Editor in the sidebar drawer, and save it as a new asset. If the user saves into a folder like “thumbnails,” they then have to locate the newly created asset (and may also need to rename it manually).

Replacing an existing image with a crop
When the Image Editor is opened via the edit button in the asset field (rather than explicitly via the sidebar drawer), the user may end up creating a new asset without knowing its storage location. On top of that, the edited result may not replace the currently selected image in the field, which makes the outcome feel inconsistent and unpredictable.

Missing feedback during saving
More generally, users get no clear feedback about where the edited image will be saved, regardless of how they entered the Image Editor. A dedicated saving step (showing destination folder + filename, and clarifying whether the action will replace the current field value or create a new asset) would significantly improve user clarity and confidence.

I'm linking what I actually found concerting this point in other discussions: #8547 and #2882

[thupsi]

+1 for this. It would provide both increased clarity and cotnrol to the author.