Support DBI specific schema handling

[eblondel]

Methods develop so far are essentially based on the default schema considered with the DBI connection. In many cases, as it is recommmended, users used specific schemas. Areas where code needs to be refactored include:

• software specification. Need to define a schema property (not specifically a DB connection parameter)
• handlers (entity, contact, dictionary)
  • entity_handler_dbi
  • entity_handler_dbi_df
  • entity_handler_dbi_geometry_columns
  • contact_handler_dbi
  • dictionary_handler_dbi
• entity enrichment
  • entity$enrichWithData,
  • entity$enrichSpatialCoverageFromDB
  • create_geoflow_data_from_dbi (to check)
• writeWorkflowJobDataResource
• actions
  • sf_write_generic (calling writeWorkflowJobDataResource)
  • sf_write_dbi (calling writeWorkflowJobDataResource)
  • geosapi_publish_ogc_services (for DB Postgis datastore on-the-fly creation with geosapi)