Changes not detected when using survey GPKG with rasters

Nobody has claimed this yet.

A problem that a user was having:
- setup: a geopackage with some survey vector layers + a raster layer with a background map
- when a feature in survey layer was modified, Input claimed no changes

The problem is that changes were not detected because the GPKG was open in WAL mode, and the local .gpkg file was unchanged compared to the basefile, so geodiff was not even run on that file.

The GPKG file was open in WAL mode - which should not happen, because we request OGR to switch to non-WAL mode. However in this case, a raster layer from the same GPKG file was loaded first, opened in WAL mode, and then OGR as the second client was unable to switch to non-WAL mode anymore...

Possible fix: turn all GPKG to non-WAL mode before opening project in Input? Or maybe make GDAL respect OGR_SQLITE_JOURNAL option as well? Or just warn users this is not supported?

Start by tracing project opening and how raster and survey vector layers access the same GPKG, then inspect the WAL-mode and geodiff comparison behavior described in the issue. Reproduce the case where the raster opens first; done should mean modifications to the survey layer are detected, with the chosen handling documented or implemented.

Written by the indexing model from the issue text.