Smooth block options migration

[labomatik]

Let's imagine we create a block v1.0 text with 3 options:
-> font-size
-> text-color
-> text-background-color

all blocks are created in the database as json
with

  {
    "data": {
      "label": "Lorem ipsum .",
      "font_size": "1rem",
      "text_color": "#000",
      "text-background_color": "transparent"
    },
    "name": "Text",
    "type": "text",
    "block": "screen.text"
  }

Let's now deploy a new version of the block v1.1
the block options is now containing a new option and add some refactoring
-> margin
-> font-size
-> text-color -> TO color
-> text-background-color -> TO background-color

When loading blocks paver will complain that color, background-color is not existing

This is adding a complexity for the maintenance of blocks.

[jeffreyvr]

Good point! Will think about this to see if that experience can be improved