Allow "upgrade" of certain template properties: select -> multiselect, text -> rich text (markdown)

[RafaPolit]

Given our new metadata structure, selects can, transparently and without any issue, become multiselects (not the other way around!!!). Text fields can also become Rich Text fields (and, in this case, loosing the formatting, perhaps also the other way around).

We should provide a way to "upgrade" this fields at any given point. It's a good quality of life improvement and costs nothing on our side.

[txau]

@RafaPolit what about rather simplifying and having only multi-select and rich text?

[RafaPolit]

Well, I think it's not enough. You really want some selects to allow only a single value. So it could be a 'select' that has option to allow single or multiple values.

With text, it's a little less clear. We could make all text rich text, but then all values would be wrapped in, at least, a <p>, and that is not necessarily something we want for really simple text fields, so not sure.

[txau]

Some other transformations are also possible:

• Numeric => text
• Text => numeric (validate data dry-run first)
• Text => thesaurus (resolve duplicates into single values)
• Numeric => thesaurus
• Thesaurus => text
• Dates => other dates (with some internal rules)
• Text => geolocation (location name to lat/long resolution)
• Geolocation => text (lat/long to location name resolution)

[RafaPolit]

This can be worked as part of the template creation redesign.