Able to push changes to original tables/layers

[antoniolocandro]

Similar to discussion here #681 with regards to postgis but I guess this will apply to any supported layer.

It would be great if it behave a little bit more like git, let's say I have an existing Postgis DB, GPKG etc, this is what others may be using or should be managed, a kart repo should be able to be started that takes this pre-existing layers and then one can work creating branches, etc.

Commits would go to the main branch but there should be an option to push the changes to the original source from where the data was imported which I think is not the case.

For a postgis db, for example I could have several schemas with tables, when initializing a kart repo I would expect the import of the tables into where kart stores the information including the ability to know to which schema they belong. Then work normally with kart and an option to push at the end if wanted the changes to the original postgis db to the respective schemas.

This would be similar workflow to GPKG or other supported formats. Don't know if this would be really possible

As it is right now, it seems once I have commited the changes to the kart repo main I would need a different process to actually export to a file or update the original ones