QGIS project should be refreshed when the conflicted project version is downloaded

What happens
In specific scenarios, QGIS uses old conflicted geopackage and not a new one. Therefore the user is not able to create new points in this layer. When a conflicted version of the project is downloaded from the mergin, geopackage is renamed to the conflicted one, and a new geopackage file is created. In this situation, when the user created a new point and hit the save button, the point is lost from the map canvas. The workaround is to close the project in QGIS and open it again.
The solution for this problem would be to refresh the project when a conflicted version of the project is downloaded.

How to reproduce

1. create a project with a point layer and open it to both mergin web and QGIS
2. add a point in QGIS, and hit save, but don't synchronize the project and close QGIS
3. from mergin web, create new version of the project by uploading updated project files from the directory on the PC
4. open QGIS and the project (don't synchronize yet), and add a new column in the layer
5. now hit synchronize, you get a conflict error ➝ this is OK
6. hit synchronize again and now the project should be synchronized between QGIS and mergin
7. try to add a new point. You should see also a newly added column in the form.
8. now hit the save button for the new point ➝ point disappear from the map (this is the problem)

Author of the original task:
Jozef Budac

Original tags:
migrate to github

Original task URL: https://app.clickup.com/t/861mt43y6

Start by reproducing the conflict-download workflow in QGIS and trace the synchronization handling after the conflicted project and geopackage are downloaded. The fix is complete when the project uses the refreshed geopackage, the newly added column appears in the form, and a newly created point remains visible after saving.