Data columns not created on config import

[mikemccaffrey]

While working on #21, I noticed that when importing config changes that involve adding additional subfields to a multifield, the data columns needed are not being added to the field_data_XXX and field_revision_XXX tables.

Either we are encountering a variation of #21 where the multifield module does not want to change the subfields after the data are in them, or we have a more fundamental problem where the module is not updating its schema based on configuration changes properly.

[mikemccaffrey]

I just ran the config update on a site with the multifield table truncated, and it still didn't seem to create the data column on the multifield field data and revision tables. That means that this has nothing to do with whether the field has data in it or not, but instead is a more fundamental problem of the table not being updated properly on config import of new multifields.