Mesh Gradients are broken in 1.5

<!-- 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: --> ... (write here) #### Steps to reproduce: <!-- Describe what you did (step-by-step) so we can reproduce: --> - open Inkscape - open [mesh_gradients.svg](/uploads/a905cf80a30c95583dc348a8f1384db7/mesh_gradients.svg) - Attempts one of these tasks: - Copy and paste one of the mesh gradients - Select one of the gradients rectangles and use Edit > Resize to Object - Look at the third mesh which is a bicubic mesh, it should look like 1.4 (see screenshot below) - Export one of the meshes by selection to an svg - Or if you open up the pdfoutput svg that this comes from and export page 6, the page will be blank #### What happened? - Empty rectangles and the mesh coordinates were not updated correctly on any of these operations - What has gone wrong with the bicubic mesh is hard to know, the transform bugs might be old but this rendering issue has appeared just in 1.5 so should be possible to narrow down the commit that caused it. #### What should have happened? ... Sample attachments: {width=414 height=406} <!-- 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: --> ``` ``` <!-- ❤️ 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. -->

task