Fixed #23609 -- Changed behavior when dropping a NULL constraint to update rows with NULL to default

Ticket: https://code.djangoproject.com/ticket/23609
Maybe a little too familiar wording? Also a suggestion of what one may want to do would be helpful, for instance: `(i.e. deal with existing NULL using a separate RunSQL or RunPython operation)`.