Workflow Version History Shows Inconsistent Timestamps and Unexpected Versions

Tested in Elsa 3.5.3 on IIS Server

## Description

When using programmatic workflow definitions, the version history sometimes appears inconsistent:

- On 17.02.2026, a new deployment was performed, but there were no changes in the workflow definition.
- The published version is Version 1, which is expected and correct.
- However, there is also a Version 2 listed, and its creation date is before the creation date of Version 1.

## Expected Behavior
- Workflow versions should be listed in chronological order.
- The creation date of a newer version should never be before that of an older version.
- If no changes are made to the workflow definition, no new version should be created, or at least the versioning and timestamps should remain consistent.

## Impact
- The version history is misleading and may cause confusion for users and administrators.
- It is unclear which version is actually the latest or should be used.
- This could potentially lead to incorrect workflow deployments or troubleshooting difficulties.