[Minor Feature Request] Add audio and/or visual feedback to clipboard actions

### Feature Description

Having a sound play out when a clipboard action occurs (copied to clipboard and loaded into paste buffer, copied to clipboard and not loaded into buffer, entry loaded from clipboard into buffer) can help with interactions between the clipboard, wayland, and isolated environments like a TTY or Flatpack app where sometimes actions fail on the first try.

### Use Case

Having a feedback that you copied properly to the clipboard or successfully loaded an entry to the buffer makes it less likely for the user to paste the wrong thing due to wayland or isolated environment issues and end up deleting the paste and redoing the process.

Having a sound play will inform the user that they don't need to press copy more times because it already succeeded, or that they copied the entry but the loaded entry is the last one and not the copied, so they know to select it at the clipboard manually.

### Compositor(s)

All compositors

### If Other, please specify

_No response_

### Proposed Solution

The easiest implementation and the cleanest in my opinion is having three sounds, one for each of the situations I described above at `Feature Description` , the only problem is for the user to understand that the "second" copy sound meant that it didn't load into buffer. With a handful of uses I think anyone will come to understand it by association but I have to agree it is not the best UX decision.
(Optionally you can have two sounds instead of three, one for when something is loaded into the buffer, no matter the origin, another for when something is just copied but not loaded)

Another option is having a small notification appear somewhere on the screen or as a toast that does not remain on history (so it won't flood notification history); this one is a little bit more intrusive and needs a bit more work depending on how the notification appears (OSD, toast, etc), but is the least confusing/ambiguous.

### Alternatives/Existing Solutions

_No response_

No files, tests, or entry points are named in the issue. First locate the clipboard action handlers in the shell and review how clipboard success and buffer loading are currently represented. Done requires an agreed feedback behavior for each listed outcome and a verified implementation across the supported compositor environments.

Written by the indexing model from the issue text.