In the new flow, it doesn't make sense to _not_ save the OS
customization parameters, so remove the ComboBox.
Additionally, our data model was failing to notify the UI of changes to
the saved settings state. Due to time constraints, I'm not able to
resolve the binding in the 'correct' manner, but I can introduce a
makeshift status signalling mechanism to prevent UI inconsistency.
Per a request from the Raspberry Pi Communications team, change
'Advanced Settings' and 'Image customization' to read 'OS
customization'.
This is to avoid amibuguity in the English, where Image_r_ and Image may
be conflated when reading at speed.
Regrettably, this breaks the existing translations. To prevent
confusion, explicitly delete the existing translations - as they're almost
certainly not valid with the reworded meaning.
This reverts commit 2fb58dc01c.
The original commit included an unexpected deletion of _all_
translations in certain languages. This was unintented, and appears to
have been a merging artefact.
This change will be re-submitted as a separate PR.
This patch carries a translation risk, as we change the default
progression button.
Remove the customisation button all together, and make the customisation
options something we offer as part of flashing an image that
has that capability.
While this adds an additional click to the flash sequence, it should
provide a steer to people who are flashing customisable images to make
use of this capability, potentially avoiding an additional pass through the
Imager.
