Legacy CSV support fixes

[saxondigital]

Tested 'bing_artistic_grid_v1' with original app (antz-msw_2012-12-09) vs current app (antz-msw_2023-01-25 v0.235.3) and found differences:

• Grid spacing was 15 units (currently is 30 units).
• Geometry was not offset for root pin topo (when not a pin geo).
  • Currently, the other (non-pin) geo's get offset 5 units on z-axis.

[saxondigital]

Add methods to more easily load legacy presets and time-stamped datasets. Currently you can load presets one file at a time using the file dialog ('L' key).

[saxondigital]

Added support to load legacy presets with v0.235.6 which supports the following file pattern naming:

• v1.0
  • .../usr/csv/ANTZ0001.CSV
• v1.1
  • .../usr/csv/antz0001.csv
  • .../usr/csv/antztag0001.csv
  • .../usr/csv/antzch0001.csv
  • .../usr/csv/antzchmap0001.csv
  • .../usr/csv/antzglobals0001.csv
• v1.2
  • .../usr/csv/antz0001globals.csv
  • .../usr/csv/antz0001node.csv
  • .../usr/csv/antz0001tag.csv
  • .../usr/csv/antzch0001.csv
  • .../usr/csv/antzchmap0001.csv
• v1.3
  • .../usr/antz0001/csv/antz0001globals.csv
  • .../usr/antz0001/csv/antz0001node.csv
  • .../usr/antz0001/csv/antz0001tag.csv
  • .../usr/antz0001/csv/antzch0001.csv
  • .../usr/antz0001/csv/antzchmap0001.csv
• v1.4
  • .../usr/_np_preset/preset001/csv/preset001_np_ch.csv
  • .../usr/_np_preset/preset001/csv/preset001_np_chmap.csv
  • .../usr/_np_preset/preset001/csv/preset001_np_globals.csv
  • .../usr/_np_preset/preset001/csv/preset001_np_node.csv
  • .../usr/_np_preset/preset001/csv/preset001_np_tag.csv
  • Additional changes:
    • .../usr/global/ renamed to .../usr/_np_global/
    • The preset folder name is fixed, but contents can be custom names, eg: MyName_np_node.csv
    • To make a custom named dataset into a preset you only need to change its base directory name and place it in the _np_preset folder, eg:
      • .../usr/mydataset/ -> .../usr/_np_preset/preset003/

*Note that older files take precedence from v1.0 -> v1.4

[saxondigital]

Note that there are sub-versions, such as variants of a node table that change the use of (existing) columns.

Related issue: #368