overlapping cue-size and normal voices should be offset

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

When cue notes and ordinary notes overlap in two voices, the cue-size notes should be automatically offset, similar to what is already done for small noteheads.

Supporting files, videos and screenshots

Here is a simple example showing two measures with two voices that overlap on the D in the second quarter note (.mscz file attached below, renamed to .zip).

• When the second voice is "cue size" in measure 1, the overlapping noteheads on the D look a bit weird (and are hard to distinguish from two normal voices overlapping).
• When the second voice uses "small noteheads" in measure 2 then they are offset and it looks a bit nicer and easier to read (but the stem sizes are wrong — we probably want cue size here and not small noteheads)

overlapping-cue.zip

An example where this sort of overlapping appears in a published score is this snippet (from Gather, 3rd. ed., hymn 692, published by GIA):

(Even though the overlapping "G" is the same note value, they probably wanted it as a separate notehead for verse 2 in order to break the beam with the following note, which is a quarter note instead of an 8th note as in verse 1.)

In which versions of MuseScore Studio is this issue present?

MuseScore Studio version (64-bit): 4.7.3-260608135, revision: github-musescore-musescore-cf9860c

Regression

Not sure.

Operating system

OS: macOS Tahoe (26.5.1), Arch.: arm64

Additional context

Taken from this discussion: https://github.com/musescore/MuseScore/issues/33959#issuecomment-4802001668, where @MarcSabatella wrote "I do vaguely recall that we special-case noteheads of different sizes and that's why "small notehead" does the offset automatically. Certainly worth considering doing that for cue as well."

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