Georeferencer visual error

[fmeier1995]

What is the bug or the crash?

There is a visual error while working with the georeferencer. It has no bad effects but it could be confusing.
see steps / video for details

Steps to reproduce the issue

1. start the georeferencer tool and add some data
2. add a point ("enter map coordinates" appears)
3. before confirming the point, pan the georeferencer-data
   the point will stay at the same position of the display, it doesn't move along with the data
   it only has visual effects, after confirming the coordinates of the point it is at the originally place

georeferencer_issue.mp4

Versions

<style type="text/css"> p, li { white-space: pre-wrap; } </style>

QGIS version	3.38.0-Grenoble	QGIS code revision	37aa618
Qt version	5.15.13
Python version	3.12.4
Compiled against GDAL/OGR	3.9.0	Running against GDAL/OGR	3.9.1
PROJ version	9.4.0
EPSG Registry database version	v11.004 (2024-02-24)
GEOS version	3.12.2-CAPI-1.18.2
SQLite version	3.45.1
PDAL version	2.6.3
PostgreSQL client version	16.2
SpatiaLite version	5.1.0
QWT version	6.2.0
QScintilla2 version	2.14.1
OS version	Windows 11 Version 2009
Active Python plugins
db_manager	0.1.20
grassprovider	2.12.99
MetaSearch	0.3.6
processing	2.12.99

QGIS version 3.38.0-Grenoble QGIS code revision [37aa618](https://github.com/qgis/QGIS/commit/37aa6188bc) Qt version 5.15.13 Python version 3.12.4 Compiled against GDAL/OGR 3.9.0 Running against GDAL/OGR 3.9.1 PROJ version 9.4.0 EPSG Registry database version v11.004 (2024-02-24) GEOS version 3.12.2-CAPI-1.18.2 SQLite version 3.45.1 PDAL version 2.6.3 PostgreSQL client version 16.2 SpatiaLite version 5.1.0 QWT version 6.2.0 QScintilla2 version 2.14.1 OS version Windows 11 Version 2009

Active Python plugins
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99

Supported QGIS version

• I'm running a supported QGIS version according to the roadmap.

New profile

• I tried with a new QGIS profile

Additional context

No response

[uclaros]

This has been previously reported as #44986 and there's a pending PR #57984 fixing it!