Ottava line placement/visibility on cross-staff beaming

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

1. Create a score using cross-staff beaming;
2. (Potentially required if spacing is too wide:) Decrease the measure width, the first note after the staff-crossing will now be placed almost vertical to the previous note;
3. Add an ottava line that should end at the staff-crossing (after the last note before the staff-crossing);

Expected behaviour:
4. There should now be an ottava with the end hook of its line placed after the last note on the original staff;

Actual behaviour:
4. There is now an ottava with the end hook of its line placed (almost completely) before the last note on the original staff;

One might try to extend the line to one of the cross-staff notes and expect the line to continue. Instead, the line disappears. The handle disappears too, so reverting the change is difficult without removing and re-adding the ottava.

5. Extend the ottava line to one of the notes crossing the staves, either using the mouse to move the handle or using the keyboard shortcuts;

Expected behaviour:
6. There should now be an ottava with the end hook of its line placed after the selected note that was moved to another staff;

Actual behaviour:
6. The ottava symbol remains, but the line and its handles disappear from the UI and the engraving.

A working example of the issues (with a .zip extension added to the .mscz file to get Github to accept it):
Ottava line placement.mscz.zip

Supporting files, videos and screenshots

The end hook of the ottava is placed before the note that it should be after:

https://github.com/user-attachments/assets/207e354b-c41f-4867-b899-17bd5eae4827

The ottava line disappears when trying to anchor the end handle at a cross-staff note:

https://github.com/user-attachments/assets/e3822b7d-d491-4126-94fb-bada28455eb9

What is the latest version of MuseScore Studio where this issue is present?

MuseScore Studio version (64-bit): 4.4.1-242490810, also tested on the latest nightly: 4.5.0-242560303, revision: github-musescore-musescore-ac76040

Regression

I was unable to check

Operating system

OS: Ubuntu 24.04 LTS, Arch.: x86_64, Format: AppImage

Additional context

Somewhat related to #16682, as part of the issue is that MuseScore Studio is, in these cases, very opportunistic (maybe too?) in placing the first note in the new staff using cross-staff beaming.

Another example of this extremely tight placement in cross-staff beaming is in this measure (also included in the attached example file)

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible