fix: remove extra undo entry when adding note

[xenonnn4w]

Purpose / Description

When undoing the note, the unlabeled entry from notetypes.save() would be exposed, causing undoAvailable() to return false and hiding previous deck operations from the undo stack.

Fixes

• Fixes "Undo Add Note" breaks the undo stack in the decks screen #19508

Approach

Remove notetypes.save() from undoableOp block as it's redundant - the note already contains notetype information.

How Has This Been Tested?

undo.mp4

Checklist

Please, go through these checks before submitting the PR.

• You have a descriptive commit message with a short title (first line, max 50 chars).
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the Google Accessibility Scanner

[BrayanDSO]

Tests fail, and that probably means that the fix is wrong.

Please run CI before making a PR. You can run it in your GH branch as well if you don't want to run it locally.

[xenonnn4w]

The saveNoteWithProgress() function was calling both notetypes.save() and addNote() inside the same undoableOp block. This created two separate backend undo entries:

• Unlabeled entry from addOrUpdateNotetype()
• Labeled "Undo Add Note" entry

When undoing the note, the unlabeled entry was exposed, causing undoAvailable() to return false and hiding previous operations.
Solution:

• Removed notetypes.save() from saveNoteWithProgress() to create only one undo entry.

Trade-off:
This breaks issue #13931 - the notetype's "last used deck" preference is no longer persisted. Users
will need to manually select the deck each time they add a note.
The test NoteEditorTest; decide by note type preference - 13931 has been disabled to accomplish this.

This is a temporary fix. The proper solution requires backend changes i.e have addNote() automatically update notetype.did,

[BrayanDSO]

The proper solution requires backend changes i.e have addNote() automatically update notetype.did,

So, we should wait for that.

[xenonnn4w]

The backend already handles "last used deck" tracking automatically via defaultDeckForNoteType().
Latest commit updates the test to use modern API - all tests passing.
Backend issue closed: ankitects/anki#4434
Ready for review!

[david-allison]

Squashed, updated commit message, fixed an unnecessary newline change, and force pushed

Thanks!!!!