This is needed in order to speed up boot procedure. For example for the kml
layer at startup we need to load the kml and its metadata based on its
url, this could be done asynchronously and then update only the kml data of
the layer and/or only the kml metadata of the layer. Before we needed to do
both together and update them together.

To allow support of local KML file, the file name is used as URL and during the
parsing of the URL parameter if the url part of the layer doesn't starts with
http then it is ignored and not added to the layer list.

I also changed a bit the isLoading logic during the parsing of the url parameter for
KML. I did this for 2 reasons:
 1. Avoid unnecessary spinner which makes the application feeling to be slow
 2. In the case of an external KML layer we cannot load the metadata and it would spin forever

Due to his isLoading changes I also updated the load kml plugin to only load
kml metadata when the kml is not external and it has missing kml metadata.

Simplified KMLLayer class constructor. The fileId can always be parsed from the
URL (for non external layer). In order to simplify the constructor which has
already quite a lots of parameter remove this one and parse it from the URL
whenever possible. Same for the isLoading and isExternal, those two can be
guessed from the other parameters.

…ade to vue 3.4

This feature has been adopted in Vue 3.4, therefore it is safe to use it now
within vue 3.3.

I tried to upgrade to Vue 3.4, but it breaks the drawing module ! Apparently
Vue 3.4 has a bug when returning a ref from a composable and watch this ref in
a component using the composable. In this case the watch is not fire when the
ref changes.

This was the case where in `useDrawingModeInteraction.composable.js` the returned
ref `lastFinishedFeature` did not fire change event on the watcher in `DawingMarkerInteraction.vue`

The menu section logic was as follow:

1. Open active layers section when a layer was added to an empty list
2. The active layers was open at startup only if the list was not empty
3. The active layers and geo catalogue section were close when opening
any other section

In this logic the active layers was never automatically re-opened unless it went
from empty to non empty.

Now the logic has been changed as follow:

1. By default the active layers is always open (at startup)
2. We have two type of sections:
  a. singleMode (formerly nonScrollable): when a section is open, all others are
     closed
  b. multiMode (formerly scrollable): when a section is open, only singleMode
     sections are closed
3. When the drawing and advanced tool section are closed, the active layer section
   is automatically open
4. When the import file tool is open, the active layer section is open (closing
  the advanced tool section)

This allow for a better user experience and feedback when adding drawing and/or
external layers

In order to debug using the browser debugger tool during cypress tests you
need to have the source map and for this you need to provide the vite config
to the cypress file pre-processor.

Also we need to have the server mode and the cypress mode in sync in order
to use our environment variable in tests, otherwise the test will get the
prod variable while the server is using the dev variables.

The Vue 3 and Vuex documentation specifies that we should only use javascript
plain object as reactive object.

Unfortunately we don't do this with our active layers that are javascript class
and put into the store. For this use case it is quite convenient and changing
this would require a big rework.

Therefore we keep the class but with a big warning. The main known issue is
that the class getter/setter cannot be reactive which leads to subtle bugs
hard to find. Reactivity could also have some issues if the class contains
side effect methods (method that set properties).

Here I removed all getter/setter and added the warning.