Previously we would remove any nodes that were at the end of
the replacement queue, which was causing some bad behavior with
nearly infinite loops unloading and reloading chunks. The strategy
has been updated to only remove nodes that we know will not be
requested again in the next scene update.

Signed-off-by: Nwulu <wulu90@outlook.com>

Fix delete curve vertex

* Update MetaSearch with new settings API

fixes #54144

* remove Arcgis Map Server

* fix test

primitives from each tile by z order before rendering them

This avoids a bunch of z order artifacts, leaving only artifacts
on tile boundaries or on overlapping tiles

progress preview render results while drawing the layer, which
differ from the final layer render

The immediate use case here is for rendering tiled scene layers.
In order to generate the actual final render for these layers,
we need to first fetch ALL content for the render and then sort
the primitives by z value. But this means that the layer renders
can be extremely slow, with no visible changes on the map until
all the content fetching is complete. Not great user experience!

Instead, here we add the infrastructure so that a layer renderer
can get a temporary image to paint to for any partial renders.
This image gets used during map composition up until the layer
finally finishes rendering, at which time the layer's actual
destination image will be used for the composition.

This means that tiled scene renderers can now draw all tiles
(with unsorted primitives, and the artifacts which come with
that) as soon as we fetch each tile. This gives the user an
immediate visual reflection that the tiles are being fetched
and that how quickly (or slowly) that is happening. As soon
as we've got all tiles, the layer render will be immediately
switched to the version in which all content is rendered
in the correct z order.

As a bonus, we draw these temporary in progress renders
over any previously transformed cache version of the layer
available. So eg when you zoom in, you'll get a zoomed in pixelated
version of the last render which gets progressively drawn
over with each tile as it is fetched.

This same API could be used in future eg with point cloud
rendering when points are being sorted by z value to give
timely visual feedback.

Don't try to draw near vertical triangles in 2d views

force the layer to be rasterised

There's no benefit in exporting these layers as a bunch of triangular
images which are pieced together, that adds a lot of extra content to
the exports and results in files which can be extremely slow to open
and render in other viewers.

When we fetch hierarchy and it leads to a bad URL, we get no content
and then we try to get the hierarchy again and again (especially
in 3D view this can trigger loads of requests). So when we failed
to get content, let's mark it as NotJson so that we do not retry
hierarchy fetch.

Move QgsWmsRestorer in QGIS Server DXF export one level up

thread)