Undoing changing project properties interferes with publishing / saving to cloud

[cbjeukendrup]

1. Create score and save it to your computer OR open score from your computer that has never been published / saved to the cloud yet
2. Change some project properties
   • for example, like in the video, change the title from "Changing the title" to "Changing the title to something else"
3. Publish the score
4. Undo
   • changes the title back to "Changing the title", but also discards the cloud save info, because it is also stored in project properties.
     (In fact, you could even say that saving to cloud corrupts the undo stack, because it modifies the project properties without informing the undo stack. But given how the ChangeMetaTags command is implemented, this does not really cause trouble, except this issue.)
5. Save the score (don't forget, because of Publishing a score marks it as saved, and undoing after that does not mark it as unsaved #17560)
6. Close the score
   • this is necessary because as long as the score is open, the cloud info is also stored in NotationProject::cloudInfo
7. Reopen the score
8. Try to publish again
   • expected: Can replace/update the previously published version of this score
   • actual: MuseScore has forgotten everything about the previously published score

Schermopname.2023-05-14.om.20.49.25.mov

Fixing this might also fix #20544.

[bkunda]

Last-minute bump to 4.3 owing to relatively niche reproduction steps and negligible negative impact on the cloud-storage end.