Latex formula clipping characters on subsequent runs (GenerateExtension doesn't handle id clashes)
<!--
See our full bug reporting guidelines at https://inkscape.org/contribute/report-bugs/
Writing a good bug report will ensure we'll be able to help efficiently. 🙂
-->
#### Summary:
<!-- Summarize the issue/suggestion concisely: -->
For specific input texts, some Latex symbols are invisible.
#### Steps to reproduce:
<!-- Describe what you did (step-by-step) so we can reproduce: -->
- open Inkscape
- click `Extensions` -> `Render` -> `Formula (pdflatex)...`
- enter Latex input: `$x \rightarrow \cos(x)$`
- set `Font size (pt)` to `10`
- click `Apply`
- set `Font size (pt)` to `30`
- click `Apply`
#### What happened?
The larger rendering is not displaying all characters.
#### What should have happened?
The generated objects/group should only differ in scale.
<details>
<summary> I dug into it... </summary>
Every character seems to have its own clipping object. In the larger rendering, some clipping objects are positioned in the wrong places. Why even is every character clipped that way? If I remove said clipping objects, the output formula looks just right.
</details>
Sample attachments:
<!-- Attach the sample file(s) highlighting the issue, if appropriate. -->

#### Version info
<!--
Open 'Help > About' and click on the little bug icon in the bottom right corner that copies the debug information to your clipboard. For command line users, run 'inkscape --debug-info'.
For Inkscape 1.0.2 and older, please manually add the Inkscape Version and Operating System Version. The Inkscape version is listed in the About dialog. For command line users, run 'inkscape -V'
Paste the information in the empty space between the apostrophes below:
-->
```
- Inkscape 1.2 (dc2aedaf03, 2022-05-15)
- Windows 10
```
<!--
❤️ Thank you for filling in a new bug report, we appreciate the help! ❤️
Please be patient while we try to find the time to look into your issue.
Remember that Inkscape is developed by volunteers in their spare time, we'll try our best to respond to all reports.
-->
<!--
Please be careful when/after writing # for example in logs, code, or versions of linux
- use inline code span - single backticks (`) before and after it, like this - `inbox#1618`
- use multi-line code block - triple backticks (```) to fence/enclose console logs
- attach long logs as a text file.
-->
issue