docker: Update GDAL to 3.13.3 because of performance regression on Linux

[ninsbl]

Working with external raster data (r.external, r.external.out) in our current docker image can be very, very slow due to a regression in GDAL 3.13.2, that is currently built in there. See for context:
https://github.com/OSGeo/gdal/blob/master/NEWS.md#port

This PR updates to the most recent GDAL 3.13.3 that fixes the regression...

[ninsbl]

BTW. Could/should we exclude full CI for changes to e.g. github actions, docker files, ...? If so I could try to come up with a PR...

[echoix]

BTW. Could/should we exclude full CI for changes to e.g. github actions, docker files, ...? If so I could try to come up with a PR...

You'll have to find a way to handle the "required checks". That allows us to enable automerge on PRs (wait that these checks are completed). Otherwise, only admin-level members can bypass the requirements

[wenzeslaus]

...or should we trigger some different checks for these? ...also Dockerfiles are checked to enforce intentional duplication with the Dockerfile in root dir.