Don't allow to delete a field if it creates a card type without front

How to reproduce:

  1. Open basic and reversed card note type
  2. open “fields”
  3. delete “Back”
  4. click save

Actual result:

  • Got a message “Card template ⁨2⁩ in notetype ‘⁨Basic (and reversed card)⁩’ has a problem.
    Expected to find a field replacement on the front of the card template.”

Expected result:

  • Either after step 3 got a message “Card template ⁨2⁩ in notetype ‘⁨Basic (and reversed card)⁩’ has a problem.
    Expected to find a field replacement on the front of the card template.”
  • Or after step 4, get a way to come back (e.g. adding back missing field. Or saving anyway)

Obviously, for this simple note type, this action makes no sens. But for more complex note type, where I way trying to delete plenty of fields, cancelling is a little bit of loss work

They are reasonable suggestions from a functionality perspective, but a bit tricky to implement with the current architecture.