Reproject schematisation

[margrietpalm]

Migrate schema such that all geometries in the schematisation have the model CRS. Migrations without epsg_code are not permitted and will raise. To allow for migrations of empty schematisations, as used in tests, custom_epsg_code is added as an argument to the upgrade function.

Added properties to retrieve the epsg_code and source object of that code from the schematisation (used by modelchecker and grid-builder).

To properly set all spatial indices the following is necessary

    op.execute(sa.text(f"SELECT RecoverGeometryColumn('{table_name}', "
                       f"'geom', {srid}, '{geom_type}', 'XY')"))
    op.execute(sa.text(f"SELECT CreateSpatialIndex('{table_name}', 'geom')"))
    op.execute(sa.text(f"SELECT RecoverSpatialIndex('{table_name}', 'geom')"))

Unfortunately, this triggers a bunch of warnings:

updateTableTriggers: "table "idx_channel_geom" already exists"
updateTableTriggers: "table "idx_connection_node_geom" already exists"
updateTableTriggers: "table "idx_cross_section_location_geom" already exists"
updateTableTriggers: "table "idx_culvert_geom" already exists"
updateTableTriggers: "table "idx_orifice_geom" already exists"
updateTableTriggers: "table "idx_pipe_geom" already exists"
updateTableTriggers: "table "idx_pump_geom" already exists"
updateTableTriggers: "table "idx_pump_map_geom" already exists"
updateTableTriggers: "table "idx_weir_geom" already exists"
updateTableTriggers: "table "idx_windshielding_1d_geom" already exists"

I played around with the RecoverGeometryColumn, CreateSpatialIndex and RecoverSpatialIndex but I could not find a combination or order that resulted in valid spatial indices without these warnings. A fresh pair of eyes is highly appreciated.

Note: this will eventually be merged on master, but current work is based on schema leftovers that will be merged with master before this one