PB-1875: links with pre-selected features do not center correctly

- Issue: In some occasions, opening a link containing both a center and pre-selected features would prioritize centering on the features rather than centering on the pre-established center. This would only occur at startup. Once the application is running, changing the URL to the one we want would set all parameters correctly

- Cause: On startup, we go through the store sync loop multiple times, and at one point, we set the features after the center, and thus override the center parameter

- Fix: If there is a `center` parameter in the query, we don't set the center on the features extent.

Author: ltkum

packages/mapviewer/src/router/storeSync/LayerParamConfig.class.js

@@ -237,7 +237,8 @@ async function getAndDispatchFeatures(to, featuresPromise, store) {
                     maxZoom: store.state.position.projection.get1_25000ZoomLevel(),
                     dispatcher: STORE_DISPATCHER_ROUTER_PLUGIN,
                 })
-            } else {
+                // if the center is not specifically set, we center on the middle of the extent
+            } else if (!query.center) {
                 const center = [
                     [(extent[0][0] + extent[1][0]) / 2],
                     [(extent[0][1] + extent[1][1]) / 2],