Description

Right now, many features in mapstore2 sadly assume that the remote is geoserver (because the feature was developed and tested only against geoserver) - and it also assumes that the remote geoserver is located at /geoserver/ which might not be the case (cf https://github.com/geosolutions-it/MapStore2/blob/master/web/client/utils/LayersUtils.js#L25)

Consequently, there are many small interoperability issues when using layers coming from non-geoserver sources (eg mapserver, mapproxy, qgis server..).

### Tasks
- [ ] #7809
- [ ] #7877
- [ ] #7879
- [ ] #9030
- [ ] #9031
- [ ] #9007

all those issues could be 'easily' solved if in the catalog/layer object there was a boolean flag which said if the remote was geoserver - the corresponding printing/loading code could then be amended to behave differently depending on the remote.

What kind of improvement you want to add? (check one with "x", remove the others)

• Minor changes to existing features

Other useful information

implementation ideas (from #7811 (comment)):

• parse GetCapabilities and look for GEOSERVERin /Service/KeywordList/Keyword but that assumes the admin doesnt change server keywords
• look for updateSequence attribute on the toplevel WMS_Capabilities XML element of GetCapabilities
• have a checkbox in the UI (checked by default, with remote is geoserver label) in the advanced catalog settings, which would set the flag on the catalog js object