screenshot flow

### Feature Description

Hi,

I’m not sure if this is intended, but the screenshotting flow feels a bit awkward. Unless a key-bind is defined for a specific set of settings, the user can’t adjust them on the fly. For example, by default, the screenshot will both save and copy, making it impossible to copy only.

The main cause seems to be that the Screenshoter was originally built as a CLI utility, with the GUI added on top. This design requires the screenshot configuration (saving, copying, or both) to be set before capture, which limits interactive choices.

Thank y'all for your work

### Use Case

_No response_

### Compositor(s)

- [ ] All compositors
- [ ] Niri
- [x] Hyprland
- [ ] MangoWC (dwl)
- [ ] Sway
- [x] Other (specify below)

### Proposed Solution

_No response_

### Alternatives/Existing Solutions

_No response_

No file, test, or entry point is named. Start by locating the screenshot flow and its save/copy configuration, then clarify the intended interactive behavior for Hyprland and other listed compositors; done should allow the requested capture choices without requiring a predefined key binding.

Written by the indexing model from the issue text.