Fix: Correct print scales even when constrainResolution is true

[sweco-seguro]

Correct print scales are now retained even when the ConstrainResolution option is true.

ConstrainResolution gets temporarily set to false when using the print component and is restored once the print component is closed.

Fixes #1934 in regard to ConstrainResolution. The scales are however still constrained by the max and min resolutions of the map, regardless of if ConstrainResolution is true or false.

[Grammostola]

It appears to work as intended, i.e if print scales are supplied then those are available in the scale dropdown, if they aren't supplied then the dropdown shows the scales of the map. I haven't seen a need or renderMode: vector for vector tiles either as I see no quality loss when employing even print scales that do not rhyme with the vector tile cache.

A question I see is a cached WMTS or WMS map with no underlying WMS and zooming with pinch or scroll. The MDK cached background map service doesn't seem to have a problem but I'm not aware of how it is setup. That map does not employ constrainResolution and the tile requests never seem to miss. If someone has a setup with a cached map that needs constrainResolution (because there is no underlying wms service) then maybe they could advice what happens without constrainResolution. If a problem then this PR could simply be a print config option.