Enable Change Tracking for cloud databases

[kristofferwebmind]

Issue description

Cms 13.4.1
Forms 13.2.4
Deploy 13.2.1

Request: Enable Change Tracking for the cloud databases

If Change Tracking is enabled, it allows us to inspect the history of the database transactions which in some cases are necessary to understand when a collision error has occured.

Background / Motivation

We have a situation where there are multiple collision errors that we can not track the origin of due to the nature of the error.
The error is that duplicates of doctypes are stored in the schema, one for a value stored only in the database and one for a value stored only on uda-file, like so:

For the first reference:

For the second reference:

For the value stored in the database (first reference above) there is no correlating uda-file.
A git command looking for the supposedly deleted file yields no results:

The only way I can think of to find out what happened and/or when it happened would be if we could see the timestamp on the value in the database.

If Change Tracking had been enabled for the database, I believe we could have seen that.

More about Change Tracking: https://learn.microsoft.com/en-us/sql/relational-databases/track-changes/about-change-tracking-sql-server?view=sql-server-ver16