Fix lengths and datatypes on sized columns, primarily in ObsCore-related schemas

The https://rubinobs.atlassian.net/browse/DM-43371 update will make the length field a requirement for columns with datatypes that are considered sized, namely char, string, unicode, and binary. This change would cause validation errors in sdm_schemas, as there are currently some columns with these types that are missing an explicit length field. For many of these, e.g., columns in the ObsCore schemas, an arraysize is present, which should instead be assigned to length.

A related issue is that there are a number of columns in the ObsCore-related schemas that have been assigned an incorrect type of char but should instead be using string. This was confirmed by looking at DDL dumped from the live version of an ObsCore database, where all such columns are VARCHAR , defined in Felis as string.

Tables affected by the above problems with lengths and datatypes include:

• dp02_obscore

• obsloctap

• oga_live_obscore

• imsim (There is just a minor fix needed here to add the length field to a single column.)

In the ObsCore-related schemas, there is an additional special case where access_url should be using the Felis text type rather than char, as the live ObsCore database uses TEXT in MySQL.