Fix #9025 WMS caching with custom scales (custom resolutions strategy from WMTS)

[allyoucanmap]

Description

This PR adds the possibility to apply custom tile grids to WMS layer through a request to a WMTS endpoint generated from a GeoServer WMS layer url. The PR includes following changes:

• add logic to WMS Layer for the OpenLayer implementation to support custom tileGrids
• add two new properties to wms layer configuration: tileGrids and tileGridStrategy
• add two new icons: grid-regular and grid-custom
• add buttons and information inline with the WMS cache options setting to toggle the custom strategy

UI Changes:

• Button to enable custom strategy

• Info icon shows information about tile grids and highlight the one in use (automatically selected)

• Info icon shows information about tile grids with warning if it's not possible to find a tile grid that matches the map projection and selected tile size

• warning when there isn't a tile grid available that matches the available projections in MapStore

• error message when is not possible to connect to the WMTS endpoint generated from the WMS layer

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https://github.com/geosolutions-it/MapStore2/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x", remove the others)

• Feature

Issue

What is the current behavior?

#9025

What is the new behavior?

It is possible to apply custom grid set configured server side to GeoServer WMS layers

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

• No

Other useful information

[offtherailz]

• I noticed that also the format and the styles may be provided. In fact if format or style do not match, you have a green light, but the tile cache misses with message "not a tile cache for requested format" ( I suppose the same for style )
  The WMTS provides this list:

<Format>image/png</Format>
<Format>image/jpeg</Format>
<Format>image/png8</Format>

So maybe we canevaluate to check also this, what do you think?

Instead style may be more complicated, you can evaluate to skip this checks.

• I suggested to simplify the messages, avoiding to talk about strategies. More information can stay in user documentation, I think. Take into accoun that if you consider also formats and/or styles, the strings change.

@tdipisa we we should not forget in doc to mention that

• MapStore automatically follow the same algorithm of GeoServer to generate the tile grids and use the cache, so most of the cases creating the tile grids with default bounding box and resolution for the tilesizes and the projections used is enough to activate caching.
• In case you are using custom tilegrids, activating the button will fetch the tilegrids and MapStore will automatically select the best tilegrid if available.

[tdipisa]

@tdipisa we we should not forget in doc to mention that

@ElenaGallo remember to open an issue for the update of the user guide.

[offtherailz]

• bug: Can't turn off the custom tile grid anymore once activated:

custom_tile_grid.webm

• One inline comment about JSDoc to update.
• Showing also the list of formats supported by the tile grid is a plus

About user experience, one thing I noticed:

Now we have a feedback of cache match only in case of custom gridset, but we do not have anything in case of standard gridset, that looks a little strange
It could make sense to check if the default strategy meets the remote gridset. Maybe the refresh button may be a check button that tells if the default strategy fits.

A more rational workflow could tell the user (if clicks on a proper button) if the standard setup works or no, and if it doesn't, he can decide to use a custom on. A workflow like this looks more rational to me, instead of having
Use cache with no feedback, and then turn on custom and see that it works or it doesn't.

[offtherailz]

LGTM. We can discuss about my last comment later.

[allyoucanmap]

@ElenaGallo please test this enhancement on dev, thanks

[ElenaGallo]

@allyoucanmap from dashboard and geostory settings panel, the 'Available tile grids' popup always reports that it's not possible to find a tile grid that matches the map projection and selected tile size.
(Use this dashboard)

aaS.mov