Bug/global setting save

Noticed this a bit late in the day (literally!). When you try to publish a global setting field to live it fails because of the empty_default_value field. I mistakenly only added this previously for programme fields, but of course globals use the same field model.

Anyway this adds in a migration. Of course the way things are right now I think I'll need to hack the test db to add the new field in.