Preserve shuffled cloze order on back

[caleblee789]

Summary

• Persist shuffle state with stable string keys instead of DOM element object keys.
• Preserve randomized cloze/list/image order when flipping from front to back.
• Regenerate note type templates from src via the repo build process.

Root Cause

The shuffle map used DOM elements as object keys. Front and back card renders use separate DOMs, so the back side could miss the original shuffle map and generate or apply a different order.

Validation

• npm run build
• git diff --check origin/master..HEAD
• Parsed generated shuffle scripts with new Function(...)
• Ran a focused replay check for duplicate cloze fields sharing the same stable shuffle keys

[caleblee789]

Example of the issue this PR fixes.

[abdnh]

I can't reproduce the issue with this particular note. Can you reproduce it if you disable add-ons (I see you have AMBOSS enabled)?

In any case, this looks like a better approach and should be more reliable if there are mutations to the key element. I assume it can still fail if for example the relative order of lists is changed in the back side for some reason, but this looks like an edge case that we don't need to worry about.

[caleblee789]

This issue occurs regardless of which add-ons are enabled. Even after disabling all add-ons, it still affects some notes. It does not occur consistently across all notes, and I have not been able to identify any specific aspect of the notes that is causing it to happen or not happen. @abdnh

[caleblee789]

Another example with addons disabled.

[abdnh]

Thank you!