fix: store updated db version instead of final target version to prevent potential issues with an update which fails half way a serie of updates

[cbos]

Description

In the InstallRepository there is a list of updates defined:

leantime/app/Domain/Install/Repositories/Install.php

Lines 41 to 76 in 6316354

	private array $dbUpdates = [
	20004,
	20100,
	20101,
	20102,
	20103,
	20104,
	20105,
	20106,
	20107,
	20108,
	20109,
	20110,
	20111,
	20112,
	20113,
	20114,
	20115,
	20116,
	20117,
	20118,
	20120,
	20121,
	20122,
	20401,
	20402,
	20405,
	20406,
	20407,
	30002,
	30003,
	30400,
	30408,
	30409,
	30410,
	];

During database schema updates this list is used to update the database schema in steps.
After each update the db-version is updated in the database, but it is directly updated to the target version in stead of the just executed updateVersion.

If one of the updates after this fails, then a check for version updates will indicate that is already all installed, while that actually is not the case yet.

Fix

Update db-version to the just updated version.
Each update will update to the new updated version, if a next update fails, next time it will try that update again.

NOTE:
I faced that the same during the development of my own plugin. I created a fix for that in my plugin and also wanted to propose a fix for the main project.

[CLAassistant]

All committers have signed the CLA.