Geopackage exporter: Remove width constraint of 32 on string fields

[leendertvanwolfswinkel]

Reason for this change: some schematisations have e.g. pumps with display names > 32 characters. Somehow they are written correctly to the geopackage, even though the field has a constraint of 32 characters max. But when we try to copy the layer later on, it leads to errors.

@jpprins1 I could not think of a reason to put a constraint on the width of string fields in the gridadmin geopackage export. So I removed it altogether. But you may have had reasons to set this 32 max width which I am not aware of.

I did test to convert a h5 file to geopackage with this new code, and it works + solves the problem outlined above

[jpprins1]

Lijkt me prima, denk dat ik het ergens weg gecopy-paste heb.

[jpprins1]

Lijkt me prima, denk dat ik het ergens weg gecopy-paste heb.