Refactor Storage in Reference Server to Support String Lookups

[darnjo]

We want enumeration data to be stored alongside other data in each table. For example, the AccessibilityFeatures field in the Property Resource should allow for data that is a multiple-enumeration.

A consideration needs to be made for the rowsize in this case since the Property Resource is already at the limit for a MySQL/MariaDB database. For this reason, TEXT fields were used for any string field that was greater than 80 characters, since TEXT is not counted like Varchar.

It's possible that JSON data types can be used, in which case the value for the multiple enumeration would be a JSON array containing the selected values for the given field.

Considerations:

• Are JSON data types treated similarly to TEXT, so that the rowsize limits won't be exceeded?
• Do JSON data types support the queries needed for the Web API spec?
  • Single-valued: These probably don't need the JSON data type, but it might be nice from a consistency perspective to use the same mechanism for both single- and multi- valued enumerations. Single-valued items need to support eq, ne,
  • Multi-valued enumerations need to support queries for any, all, and in.

[darnjo]

This is waiting on RESOStandards/web-api-commander#153.