Stroke-style related PDF export bug
<!--
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: -->
PDF export does not work or export (randomly) only part of the file or sometimes just empty page.
#### Steps to reproduce:
<!-- Describe what you did (step-by-step) so we can reproduce: -->
- open Inkscape
- just try to export attached svg to PDF.
#### What happened?
Exported PDF file is different from what is visible in Inkscape or empty
#### What should have happened?
Exported PDF file should be the same as svg source.
Sample attachments:
<!-- Attach the sample file(s) highlighting the issue, if appropriate. -->
Source file: [Rubion-test.svg](/uploads/5b9ea0decd4ab882a1c59c79c445599c/Rubion-test.svg)
Export result: [Rubion-test.pdf](/uploads/a7c25d404c15159f6e5971d2db001013/Rubion-test.pdf)
#### 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. (If it is absent, you are likely running an older version of Inkscape. Please update to the latest version and report if the issue persists.)
For command line users, run 'inkscape --debug-info'.
Paste the information in the empty space between the apostrophes below:
-->
```
Inkscape 1.4-beta (62f545ba5e, 2024-04-22)
```
<!--
❤️ 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 - `#1618`
- use multi-line code block - triple backticks (```) to fence/enclose console logs
- attach long logs as a text file.
-->
issue