Default Application Context Setting

[tdipisa]

Description

It must be possible to set up an application context as a default context for MS (the default context is always publicly readable). The default context will be used as default from MS home while a new map is created or for all contex's maps when a context is deleted (see #5149, point number 3).
This enhancement will allow to setup a default context from UI without using the standard one from local configuration file. As general constraint a default group must respect the following rules:

• The save plugin must be present
• The Catalog plugin must be present

The above constraints ensure to create a map from an existing context with a viewer that contains the needed plugins to add new contents (layers and backgrounds) and ovbiously to save the map itself.

A new checkbox could be included in the wizard step 1 of the context for this.

Other useful information

[tdipisa]

from @offtherailz

Suggested implementation (please @mbarto comment on this) :

• allow to admin to edit a configuration that indicates the default context in localConfig.json (setting a property on the server, with new back-end functionalities).
• when download localConfig.json, if this property is set, download the context.

[tdipisa]

From @mbarto

@offtherailz @tdipisa it should be possible to:

• use the existing ConfigLoader service to inject the default context and store it on a separate properties file on the server (we need to add support for multiple override property files, currently we use the georchestra default.properties for this kind of things; we also need a service to set the default context from the UI); if we prefer to use a geostore resource instead of a property file, additional support is needed
• eventually customize / improve the existing ConfigLoader service to automatically merge the standard localConfig.json with the default context json, instead of doing this on the client