a single GeoPackage file in a Mergin project is treated as an equivalent of a database schema - both can contain
multiple tables with data
after the initialization, DB sync tool uses "main" schema in database (where any user editing may happen)
and "base" schema (where only DB sync tool is allowed to do changes)
the "base" schema contains the same data as the most recently known project version in Mergin, and it is used
to figure out whether there have been any changes in the database - if there were, they will be pushed
to the appropriate GeoPackage in Mergin project