Add copy button to graphs/diagrams to copy source
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Collaborate/take over this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=409451)
</details>
<!--IssueSummary end-->
As discussed in https://gitlab.com/gitlab-org/gitlab/-/issues/409451#note_1375960637, we should be adding a copy button to the graph/diagrams in order to copy the source code, as we do for Mermaid diagrams.
---
## Implementation Guide
We want to add a "Copy to clipboard" button for all diagrams. We already support if for mermaid diagrams (when you mouse over the diagram you see the icon appear in the upper right corner of the diagram)
```mermaid
graph TD;
A-->B;
A-->C;
B-->D;
C-->D;
```
but we don't for PlantUML
```plantuml
Bob -> Alice: Hello
```
In general, code blocks have this button added in automatically, which was added in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/75433+.
It wasn't working properly for mermaid diagrams, and was fixed in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/83202+.
I don't know exactly where to fix this at the moment - it will require a little more investigation.
---
_original proposal_
### Proposal
<!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. -->
<!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.
-->
Comments can contain complex diagrams that are impossible to copy/update in another comment without the raw version of the diagram (source code).
`Maintainers` can edit comments and fetch what they need, but anyone below this permission grade can't, which includes the common `Developer` role.
Issue descriptions can be edited by Developers, so anything in there can be seen as raw and this issue is focusing on comments only.
We could add a `View raw comment` link in this comment menu:

For example: I can't suggest an edit to https://gitlab.com/gitlab-org/gitlab-web-ide/-/issues/141#note_1367835573 if I wanted to.
<!-- Label reminders
Use the following resources to find the appropriate labels:
- Use only one tier label choosing the lowest tier this is intended for
- https://gitlab.com/gitlab-org/gitlab/-/labels
- https://about.gitlab.com/handbook/product/categories/features/
-->
issue