Transposing a score with chord selection in selection filter

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

1. Create a new score (just tremble staff is enough.
2. Create a simple chord (C-E-G)
3. Deselect all notes.
4. Open Transpose Form (Tools -> Transpose)
5. Select "To Key" and select "D major / B Minor"
6. Click OK

Actual behavior:
Score is transposed, key signature is 2 sharps and chord becomes D-F#-A

Expected behavior
Actual behavior is expected behavior

6. Select the measure with chord.
7. Open the selection filter (View -> Selection filter)
8. In the Chords section deselect "Second note"
9. Deselect everything
10. Open the Transpose Form (Tools -> Transpose)
11. Select "To Key" and select "F major / D Minor"
12. Click OK

Actual behavior
Key signature becomes 1 flat and chord becomes F-F#-C

Expected behavior
Chord should be F-A-C

It seems Transpose takes the selection filter into account. Since the "Second note" was disabled everything expect the second note in chords is transposed.
Since transpose is transposing selected notes if notes are selected but everything is nothing is selected this behavior in counter intuitive and confusing. It can easy result is destroyed scores because after transposing a full score the full score is not transposed and it is not obvious to see.

Supporting files, videos and screenshots

Proposal:
If nothing is selected, transpose should ignore the chord note selection in the selection filter.
However what is a range is selected and only this range should be transposed, should the chord note selection in the selection filter also be ignored?
An alternative could be a warning in the Transpose Form if chord selection filter notes with an option to overwrite these chord selection option.

In which versions of MuseScore Studio is this issue present?

OS: openSUSE Tumbleweed, Arch.: x86_64, MuseScore Studio version (64-bit): 4.7.0-260513133, revision: github-musescore-musescore-9989a50

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

openSUSE Tumbleweed

Additional context

No response

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