Expression text in grand staff does not offset above cresc. and decresc.

### Issue type UX/Interaction bug (incorrect behaviour) ### Description with steps to reproduce Using a grand staff instrument ie. Grand Piano, Write a line of music in both staffs Add a dynamic at the start of M1 and M2 Add a Cresc or decres over bar 1 into count 1 of bar 2 Add Expression text to beat 1 of M1 Incorrect behavior for placement. Should not move the Cresc or decresc but rather offset the grand staff for that line of music on the page and have the expression text above the cresc. So offset from dynamic markings to the right, then offset up for hair pins. The best way to implement this would be, let us be able to select if we want it in the center with the dynamics, above as per my earlier description, or below, if wanted. This can be implemented into the properties menu. This fix for behavior would go very far for cleaning up grand staff notation. As of now, I don't believe MS4 can handle this use case. This is labeled as bug because expression text is an already an in place system. ### Supporting files, videos and screenshots Bar of MS4 that has this issue, <img width="519" height="500" alt="Image" src="https://github.com/user-attachments/assets/b2ad8ca1-8112-4f29-ac36-a5698e4bfe32" /> Bar of notation found online with correct placement for expression text. <img width="105" height="95" alt="Image" src="https://github.com/user-attachments/assets/3b8a2dc6-ceaa-40a6-9f65-e52766f4d785" /> ### In which versions of MuseScore Studio is this issue present? 4.7.4 ### Regression I was unable to check ### Operating system Windows 10, presumed to be all current versions of MS4.7.4 ### Additional context Conductors are very picky on how scores look. If this can be addressed as a simple implementation and pushed out to users, I would really appreciate it! ### Checklist - [x] This report follows the [guidelines](https://github.com/musescore/MuseScore/wiki/Reporting-bugs-and-issues) for reporting bugs and issues - [x] I have verified that this issue has not been logged before, by searching the [issue tracker](https://github.com/musescore/MuseScore/issues) for similar issues - [x] I have attached all requested files and information to this report - [x] I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible