[layer] maelstro must not tick the checkbox "customizeFeatureType"

[MaelREBOUX]

We discover that actually maelstro automatically check the box "customizeFeatureType" on the target GeoServer although it is not set on the source GeoServer.

So maelstro does not respect the configuration of the original layer !

We discovered that when the "customized attributes" is activated it freezes the list of the attributes even if there is new attributes added on the table in the database !

We mainly use SQL datasource as "SELECT * FROM my_table" for our layers.

[MaelREBOUX]

Note for later : divergence of behavior between IHM publication and API publication??

[f-necas]

The layer is added with the box checked by default because:

• Requesting a feature type always returns the attribute list
• Inserting via a PUT request to geoserver/rest/workspaces/psc/datastores/datafeeder_psc/featuretypes/antenne.xml ingests these attributes
• In geoserver, if the attribute list is not empty, the box is checked: https://github.com/georchestra/geoserver/blob/main/src/web/core/src/main/java/org/geoserver/web/data/resource/FeatureResourceConfigurationPanel.java#L89

The only possible solution is to remove the attribute list before inserting the feature type, which allows them all to be displayed by default.

The downside: this will have the opposite effect, meaning that if the box is checked on the source geoserver, it will not be checked on the destination geoserver.

Once the featureType is inserted, it seems that we can no longer really edit the attributes via the API. Geoserver doesn't seem to have taken this into account.

[MaelREBOUX]

The #97 PR fixes the wrong behaviour. Available in the 0.1.4 release.

So now, by default the publisheb layer on the target GeoServer will not have custom atrributes.
(think to put this in the documentation).